Check Defect Detection

The CFM service allows different types of defects to be detected in the network through the processing of CFM datagrams received on a network interface. The following scenarios show how, with different configurations, these defects are detected, and how to configure the service to avoid detecting certain defects.

../../../_images/topology17.svg

Detect XconCCM Defect Due To Low Level

Description

In this scenario, a CFM service with domain level 6 is configured in DUT0. However, in DUT1 a CFM service with domain level 5 is configured. This causes CFM datagrams to be received in DUT0 with a domain level lower than its own and, consequently, XconCCM type defects are detected.

Scenario

Step 1: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.0.0.1/24

Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.0.0.2/24

Step 3: Set the following configuration in DUT0:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 rmep 20

Step 4: Set the following configuration in DUT1:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 5
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 rmep 10

Note

After a few seconds, the CFM service of DUT0 should detect a DefXconCCM defect.

Step 5: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: up
FNG state: defect reported
FNG current defect: DefXconCCM
FNG last reported defect: DefXconCCM
\s+20\s+failed\s+0\s+down\s+not available\s+not available
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: up
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: defect reported
FNG current defect: DefXconCCM
FNG last reported defect: DefXconCCM
Last sent sequence number: 5
Out-of-sequence CCMs: 0
Remote MEPs: 1

-----------------------------------------------------------------------------------------------------------------
rMepID  SenderID  MAC-address  Status  LastSeqNum  RDI       Port         Interface             LastTime
-----------------------------------------------------------------------------------------------------------------
    20                         failed           0  down  not available  not available  2024-06-20 18:10:38.756662

Step 6: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

true
Show output
-----------------------------------------------------------------------------------------------------
  Alarm     Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
-----------------------------------------------------------------------------------------------------
TEST_ALARM  true    2024-06-20 18:10:41.245529  2024-06-20 18:10:37.273373             2        24.02

Note

After reconfiguring the CFM service with domain level 6 in DUT1, DUT0 will no longer receive CFM datagrams with a domain level lower than its own and, consequently, XconCCM type defects will no longer be detected.

Step 7: Set the following configuration in DUT1:

set service cfm domain TEST_DOMAIN level 6

Note

After a few seconds, the CFM service of DUT0 should not detect any defects.

Step 8: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: down
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefXconCCM
\s+20\s+osdx\s+([a-fA-F0-9]{2}:){5}[a-fA-F0-9]{2}\s+ok\s+\d+\s+down\s+up\s+up
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: down
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefXconCCM
Last sent sequence number: 11
Out-of-sequence CCMs: 0
Remote MEPs: 1

----------------------------------------------------------------------------------------------------------
rMepID  SenderID     MAC-address     Status  LastSeqNum  RDI   Port  Interface           LastTime
----------------------------------------------------------------------------------------------------------
    20      osdx  de:ad:be:ef:6c:20      ok           5  down    up         up  2024-06-20 18:10:42.959956

Step 9: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

false
Show output
-----------------------------------------------------------------------------------------------------
  Alarm     Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
-----------------------------------------------------------------------------------------------------
TEST_ALARM  false   2024-06-20 18:10:48.810689  2024-06-20 18:10:41.245529             3        64.70

Detect XconCCM Defect Due To Wrong MAID

Description

In this scenario, a CFM service with Maintenance Association (MA) TEST_SERVICE is configured in DUT0. However, in DUT1 a CFM service with MA OTHER_TEST_SERVICE is configured. This causes CFM datagrams to be received in DUT0 with a wrong Maintenance Association Identifier (MAID) and, consequently, XconCCM type defects are detected.

Scenario

Step 1: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.0.0.1/24

Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.0.0.2/24

Step 3: Set the following configuration in DUT0:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 rmep 20

Step 4: Set the following configuration in DUT1:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service OTHER_TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service OTHER_TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service OTHER_TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service OTHER_TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service OTHER_TEST_SERVICE mep 20 interface eth0
set service cfm domain TEST_DOMAIN service OTHER_TEST_SERVICE mep 20 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service OTHER_TEST_SERVICE mep 20 rmep 10

Note

After a few seconds, the CFM service of DUT0 should detect a DefXconCCM defect.

Step 5: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: up
FNG state: defect reported
FNG current defect: DefXconCCM
FNG last reported defect: DefXconCCM
\s+20\s+failed\s+0\s+down\s+not available\s+not available
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: up
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: defect reported
FNG current defect: DefXconCCM
FNG last reported defect: DefXconCCM
Last sent sequence number: 4
Out-of-sequence CCMs: 0
Remote MEPs: 1

-----------------------------------------------------------------------------------------------------------------
rMepID  SenderID  MAC-address  Status  LastSeqNum  RDI       Port         Interface             LastTime
-----------------------------------------------------------------------------------------------------------------
    20                         failed           0  down  not available  not available  2024-06-20 18:11:00.987705

Step 6: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

true
Show output
-----------------------------------------------------------------------------------------------------
  Alarm     Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
-----------------------------------------------------------------------------------------------------
TEST_ALARM  true    2024-06-20 18:11:03.544488  2024-06-20 18:10:59.500709             2         9.29

Note

After reconfiguring the CFM service with MA TEST_SERVICE in DUT1, DUT0 will no longer receive CFM datagrams with a wrong MAID and, consequently, XconCCM defects will no longer be detected.

Step 7: Set the following configuration in DUT1:

del service cfm domain TEST_DOMAIN service OTHER_TEST_SERVICE
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 rmep 10

Note

After a few seconds, the CFM service of DUT0 should not detect any defects.

Step 8: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: down
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefXconCCM
\s+20\s+osdx\s+([a-fA-F0-9]{2}:){5}[a-fA-F0-9]{2}\s+ok\s+\d+\s+down\s+up\s+up
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: down
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefXconCCM
Last sent sequence number: 11
Out-of-sequence CCMs: 0
Remote MEPs: 1

----------------------------------------------------------------------------------------------------------
rMepID  SenderID     MAC-address     Status  LastSeqNum  RDI   Port  Interface           LastTime
----------------------------------------------------------------------------------------------------------
    20      osdx  de:ad:be:ef:6c:20      ok           5  down    up         up  2024-06-20 18:11:05.191324

Step 9: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

false
Show output
-----------------------------------------------------------------------------------------------------
  Alarm     Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
-----------------------------------------------------------------------------------------------------
TEST_ALARM  false   2024-06-20 18:11:10.293653  2024-06-20 18:11:03.544488             3        57.59

Detect ErrorCCM Defect Due To Same MepID

Description

In this scenario, a CFM service with MEP Identifier (MepID) 10 is configured in DUT0. Likewise, in DUT1 a CFM service with MepID 10 is configured. This causes CFM datagrams to be received in DUT0 with a MepID equal to its own and, consequently, ErrorCCM defects are detected.

Scenario

Step 1: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.0.0.1/24

Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.0.0.2/24

Step 3: Set the following configuration in DUT0:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 rmep 20

Step 4: Set the following configuration in DUT1:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 rmep 20

Note

After a few seconds, the CFM service of DUT0 should detect a DefErrorCCM defect.

Step 5: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: up
FNG state: defect reported
FNG current defect: DefErrorCCM
FNG last reported defect: DefErrorCCM
\s+20\s+failed\s+0\s+down\s+not available\s+not available
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: up
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: defect reported
FNG current defect: DefErrorCCM
FNG last reported defect: DefErrorCCM
Last sent sequence number: 5
Out-of-sequence CCMs: 0
Remote MEPs: 1

-----------------------------------------------------------------------------------------------------------------
rMepID  SenderID  MAC-address  Status  LastSeqNum  RDI       Port         Interface             LastTime
-----------------------------------------------------------------------------------------------------------------
    20                         failed           0  down  not available  not available  2024-06-20 18:11:22.068358

Step 6: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

true
Show output
-----------------------------------------------------------------------------------------------------
  Alarm     Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
-----------------------------------------------------------------------------------------------------
TEST_ALARM  true    2024-06-20 18:11:24.616435  2024-06-20 18:11:20.585360             2        23.93

Note

After reconfiguring the CFM service with MepID 20 in DUT1, DUT0 will no longer receive CFM datagrams with a MepID equal to its own. Consequently, ErrorCCM defects will no longer be detected.

Step 7: Set the following configuration in DUT1:

del service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 rmep 10

Note

After a few seconds, the CFM service of DUT0 should not detect any defects.

Step 8: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: down
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefErrorCCM
\s+20\s+osdx\s+([a-fA-F0-9]{2}:){5}[a-fA-F0-9]{2}\s+ok\s+\d+\s+down\s+up\s+up
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: down
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefErrorCCM
Last sent sequence number: 11
Out-of-sequence CCMs: 0
Remote MEPs: 1

----------------------------------------------------------------------------------------------------------
rMepID  SenderID     MAC-address     Status  LastSeqNum  RDI   Port  Interface           LastTime
----------------------------------------------------------------------------------------------------------
    20      osdx  de:ad:be:ef:6c:20      ok           5  down    up         up  2024-06-20 18:11:26.583821

Step 9: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

false
Show output
-----------------------------------------------------------------------------------------------------
  Alarm     Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
-----------------------------------------------------------------------------------------------------
TEST_ALARM  false   2024-06-20 18:11:32.219065  2024-06-20 18:11:24.616435             3        63.49

Detect ErrorCCM Defect Due To Wrong Interval

Description

In this scenario, a CFM service with interval 1s is configured in DUT0. However, in DUT1 a CFM service with interval 10s is configured. This causes CFM datagrams to be received in DUT0 with a wrong interval and, consequently, ErrorCCM defects are detected.

Scenario

Step 1: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.0.0.1/24

Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.0.0.2/24

Step 3: Set the following configuration in DUT0:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 rmep 20

Step 4: Set the following configuration in DUT1:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 10s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 rmep 10

Note

After a few seconds, the CFM service of DUT0 should detect a DefErrorCCM defect.

Step 5: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: up
FNG state: defect reported
FNG current defect: DefErrorCCM
FNG last reported defect: DefErrorCCM
\s+20\s+failed\s+0\s+down\s+not available\s+not available
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: up
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: defect reported
FNG current defect: DefErrorCCM
FNG last reported defect: DefErrorCCM
Last sent sequence number: 5
Out-of-sequence CCMs: 0
Remote MEPs: 1

-----------------------------------------------------------------------------------------------------------------
rMepID  SenderID  MAC-address  Status  LastSeqNum  RDI       Port         Interface             LastTime
-----------------------------------------------------------------------------------------------------------------
    20                         failed           0  down  not available  not available  2024-06-20 18:11:44.262313

Step 6: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

true
Show output
-----------------------------------------------------------------------------------------------------
  Alarm     Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
-----------------------------------------------------------------------------------------------------
TEST_ALARM  true    2024-06-20 18:11:46.801775  2024-06-20 18:11:42.772381             2        24.62

Note

After reconfiguring the CFM service with interval 1s in DUT1, DUT0 will no longer receive CFM datagrams with a wrong interval. Consequently, ErrorCCM defects will no longer be detected.

Step 7: Set the following configuration in DUT1:

set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s

Note

After a few seconds, the CFM service of DUT0 should not detect any defects.

Step 8: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: down
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefErrorCCM
\s+20\s+osdx\s+([a-fA-F0-9]{2}:){5}[a-fA-F0-9]{2}\s+ok\s+\d+\s+down\s+up\s+up
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: down
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefErrorCCM
Last sent sequence number: 39
Out-of-sequence CCMs: 0
Remote MEPs: 1

----------------------------------------------------------------------------------------------------------
rMepID  SenderID     MAC-address     Status  LastSeqNum  RDI   Port  Interface           LastTime
----------------------------------------------------------------------------------------------------------
    20      osdx  de:ad:be:ef:6c:20      ok          33  down    up         up  2024-06-20 18:11:48.569900

Step 9: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

false
Show output
-----------------------------------------------------------------------------------------------------
  Alarm     Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
-----------------------------------------------------------------------------------------------------
TEST_ALARM  false   2024-06-20 18:12:21.958746  2024-06-20 18:11:46.801775             3        89.36

Detect ErrorCCM Defect Due To Unknown Remote MepID

Description

In this scenario, a CFM service with remote MepID 20 is configured in DUT0. However, in DUT1, a CFM service with MepID 30 is configured. This causes CFM datagrams to be received in DUT0 with an unknown remote MepID. Consequently, ErrorCCM defects are detected.

Scenario

Step 1: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.0.0.1/24

Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.0.0.2/24

Step 3: Set the following configuration in DUT0:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 rmep 20

Step 4: Set the following configuration in DUT1:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 30 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 30 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 30 rmep 10

Note

After a few seconds, the CFM service of DUT0 should detect a DefErrorCCM defect.

Step 5: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: up
FNG state: defect reported
FNG current defect: DefErrorCCM
FNG last reported defect: DefErrorCCM
\s+20\s+failed\s+0\s+down\s+not available\s+not available
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: up
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: defect reported
FNG current defect: DefErrorCCM
FNG last reported defect: DefErrorCCM
Last sent sequence number: 4
Out-of-sequence CCMs: 0
Remote MEPs: 1

-----------------------------------------------------------------------------------------------------------------
rMepID  SenderID  MAC-address  Status  LastSeqNum  RDI       Port         Interface             LastTime
-----------------------------------------------------------------------------------------------------------------
    20                         failed           0  down  not available  not available  2024-06-20 18:12:34.300561

Step 6: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

true
Show output
-----------------------------------------------------------------------------------------------------
  Alarm     Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
-----------------------------------------------------------------------------------------------------
TEST_ALARM  true    2024-06-20 18:12:36.856714  2024-06-20 18:12:32.825039             2         7.38

Note

After reconfiguring the CFM service with MepID 20 in DUT1, DUT0 will no longer receive CFM datagrams with an unknown remote MepID. Consequently, ErrorCCM defects will no longer be detected.

Step 7: Set the following configuration in DUT1:

del service cfm domain TEST_DOMAIN service TEST_SERVICE mep 30
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 rmep 10

Note

After a few seconds, the CFM service of DUT0 should not detect any defects.

Step 8: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: down
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefErrorCCM
\s+20\s+osdx\s+([a-fA-F0-9]{2}:){5}[a-fA-F0-9]{2}\s+ok\s+\d+\s+down\s+up\s+up
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: down
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefErrorCCM
Last sent sequence number: 10
Out-of-sequence CCMs: 0
Remote MEPs: 1

----------------------------------------------------------------------------------------------------------
rMepID  SenderID     MAC-address     Status  LastSeqNum  RDI   Port  Interface           LastTime
----------------------------------------------------------------------------------------------------------
    20      osdx  de:ad:be:ef:6c:20      ok           5  down    up         up  2024-06-20 18:12:37.876126

Step 9: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

false
Show output
-----------------------------------------------------------------------------------------------------
  Alarm     Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
-----------------------------------------------------------------------------------------------------
TEST_ALARM  false   2024-06-20 18:12:43.612379  2024-06-20 18:12:36.856714             3        61.38

Avoid Detect ErrorCCM Defect

Description

In this scenario, a CFM service with remote MepID 20 is configured in DUT0. In DUT1, a CFM service with MepID 30 is configured. This causes CFM datagrams to be received in DUT0 with an unknown remote MepID. Consequently, ErrorCCM defects are detected. However, the CFM service can be configured so that it doesn’t detect defects under a certain priority level. Since the ErrorCCM defect has a priority of 4, by configuring a minimum detection level of 5 in DUT0, ErrorCCM defects are not detected.

Scenario

Step 1: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.0.0.1/24

Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.0.0.2/24

Step 3: Set the following configuration in DUT0:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 rmep 20
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm min-notification-level 5

Step 4: Set the following configuration in DUT1:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 30 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 30 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 30 rmep 10

Note

After a few seconds, the CFM service of DUT0 should not detect any defects.

Step 5: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: down
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefNone
\s+20\s+failed\s+0\s+down\s+not available\s+not available
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: down
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefNone
Last sent sequence number: 11
Out-of-sequence CCMs: 0
Remote MEPs: 1

-----------------------------------------------------------------------------------------------------------------
rMepID  SenderID  MAC-address  Status  LastSeqNum  RDI       Port         Interface             LastTime
-----------------------------------------------------------------------------------------------------------------
    20                         failed           0  down  not available  not available  2024-06-20 18:12:55.467829

Step 6: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

false
Show output
---------------------------------------------------------------------------------------
  Alarm     Status           Toggled            Prev-toggled  Toggle-count  Time up (%)
---------------------------------------------------------------------------------------
TEST_ALARM  false   2024-06-20 18:12:53.978371                           1         0.65

Detect RemoteCCM Defect

Description

In this scenario, a CFM service with remote MepID 20 is configured in DUT0. However, in DUT1 the CFM service is not configured. This causes CFM datagrams of the expected remote MepID to not be received in DUT0. Consequently, RemoteCCM errors are detected.

Scenario

Step 1: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.0.0.1/24

Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.0.0.2/24

Step 3: Set the following configuration in DUT0:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 rmep 20

Note

After a few seconds, the CFM service of DUT0 should detect a DefRemoteCCM defect.

Step 4: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: up
FNG state: defect reported
FNG current defect: DefRemoteCCM
FNG last reported defect: DefRemoteCCM
\s+20\s+failed\s+0\s+down\s+not available\s+not available
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: up
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: defect reported
FNG current defect: DefRemoteCCM
FNG last reported defect: DefRemoteCCM
Last sent sequence number: 4
Out-of-sequence CCMs: 0
Remote MEPs: 1

-----------------------------------------------------------------------------------------------------------------
rMepID  SenderID  MAC-address  Status  LastSeqNum  RDI       Port         Interface             LastTime
-----------------------------------------------------------------------------------------------------------------
    20                         failed           0  down  not available  not available  2024-06-20 18:13:17.251975

Step 5: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

true
Show output
-----------------------------------------------------------------------------------------------------
  Alarm     Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
-----------------------------------------------------------------------------------------------------
TEST_ALARM  true    2024-06-20 18:13:19.790274  2024-06-20 18:13:15.755894             2        18.81

Note

After configuring the CFM service with MepID 20 in DUT1, DUT0 will receive CFM datagrams with the expected remote MepID. Consequently, RemoteCCM defects will no longer be detected.

Step 6: Set the following configuration in DUT1:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 rmep 10

Note

After a few seconds, the CFM service of DUT0 should not detect any defects.

Step 7: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: down
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefRemoteCCM
\s+20\s+osdx\s+([a-fA-F0-9]{2}:){5}[a-fA-F0-9]{2}\s+ok\s+\d+\s+down\s+up\s+up
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: down
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefRemoteCCM
Last sent sequence number: 9
Out-of-sequence CCMs: 0
Remote MEPs: 1

----------------------------------------------------------------------------------------------------------
rMepID  SenderID     MAC-address     Status  LastSeqNum  RDI   Port  Interface           LastTime
----------------------------------------------------------------------------------------------------------
    20      osdx  de:ad:be:ef:6c:20      ok           3  down    up         up  2024-06-20 18:13:22.171678

Step 8: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

false
Show output
-----------------------------------------------------------------------------------------------------
  Alarm     Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
-----------------------------------------------------------------------------------------------------
TEST_ALARM  false   2024-06-20 18:13:24.711045  2024-06-20 18:13:19.790274             3        49.08

Avoid Detect RemoteCCM Defect

Description

In this scenario, a CFM service with remote MepID 20 is configured in DUT0. But, in DUT1, the CFM service is not configured. This causes CFM datagrams of the expected remote MepID to not be received in DUT0 and, consequently, RemoteCCM errors are detected. However, the CFM service can be configured so that it doesn’t detect defects under a certain priority level. Since the RemoteCCM defect has a priority of 3, by configuring a minimum detection level of 4 in DUT0, RemoteCCM errors are not detected.

Scenario

Step 1: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.0.0.1/24

Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.0.0.2/24

Step 3: Set the following configuration in DUT0:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 rmep 20
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm min-notification-level 4

Note

After a few seconds, the CFM service of DUT0 should not detect any defects.

Step 4: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: down
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefNone
\s+20\s+failed\s+0\s+down\s+not available\s+not available
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: down
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefNone
Last sent sequence number: 10
Out-of-sequence CCMs: 0
Remote MEPs: 1

-----------------------------------------------------------------------------------------------------------------
rMepID  SenderID  MAC-address  Status  LastSeqNum  RDI       Port         Interface             LastTime
-----------------------------------------------------------------------------------------------------------------
    20                         failed           0  down  not available  not available  2024-06-20 18:13:37.079101

Step 5: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

false
Show output
---------------------------------------------------------------------------------------
  Alarm     Status           Toggled            Prev-toggled  Toggle-count  Time up (%)
---------------------------------------------------------------------------------------
TEST_ALARM  false   2024-06-20 18:13:35.605391                           1         0.85

Detect RDICCM Defect

Description

In this scenario, a CFM service with MepID 10 is configured in DUT0. However, in DUT1, a CFM service with no remote MepID is configured. This causes DUT1 to detect a defect and activate its RDI flag, which also causes DUT0 to receive CFM datagrams with the RDI flag in UP. Consequently, RDICCM defects are detected.

Scenario

Step 1: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.0.0.1/24

Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.0.0.2/24

Step 3: Set the following configuration in DUT0:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 rmep 20

Step 4: Set the following configuration in DUT1:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 alarm TEST_ALARM

Note

After a few seconds, the CFM service of DUT0 should detect a DefRDICCM defect.

Step 5: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: down
FNG state: defect reported
FNG current defect: DefRDICCM
FNG last reported defect: DefRDICCM
\s+20\s+osdx\s+([a-fA-F0-9]{2}:){5}[a-fA-F0-9]{2}\s+ok\s+\d+\s+up\s+up\s+up
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: down
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: defect reported
FNG current defect: DefRDICCM
FNG last reported defect: DefRDICCM
Last sent sequence number: 4
Out-of-sequence CCMs: 0
Remote MEPs: 1

---------------------------------------------------------------------------------------------------------
rMepID  SenderID     MAC-address     Status  LastSeqNum  RDI  Port  Interface           LastTime
---------------------------------------------------------------------------------------------------------
    20      osdx  de:ad:be:ef:6c:20      ok           3   up    up         up  2024-06-20 18:13:57.914030

Step 6: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

true
Show output
-----------------------------------------------------------------------------------------------------
  Alarm     Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
-----------------------------------------------------------------------------------------------------
TEST_ALARM  true    2024-06-20 18:14:01.509219  2024-06-20 18:13:56.605112             2         4.60

Note

After configuring the CFM service with remote MepID 10 in DUT1, DUT0 will receive CFM datagrams with the RDI flag in DOWN. Consequently, RDICCM defects will no longer be detected.

Step 7: Set the following configuration in DUT1:

set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 rmep 10

Note

After a few seconds, the CFM service of DUT0 should not detect any defects.

Step 8: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: down
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefRDICCM
\s+20\s+osdx\s+([a-fA-F0-9]{2}:){5}[a-fA-F0-9]{2}\s+ok\s+\d+\s+down\s+up\s+up
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: down
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefRDICCM
Last sent sequence number: 9
Out-of-sequence CCMs: 0
Remote MEPs: 1

----------------------------------------------------------------------------------------------------------
rMepID  SenderID     MAC-address     Status  LastSeqNum  RDI   Port  Interface           LastTime
----------------------------------------------------------------------------------------------------------
    20      osdx  de:ad:be:ef:6c:20      ok           3  down    up         up  2024-06-20 18:13:57.914030

Step 9: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

false
Show output
-----------------------------------------------------------------------------------------------------
  Alarm     Status           Toggled                   Prev-toggled         Toggle-count  Time up (%)
-----------------------------------------------------------------------------------------------------
TEST_ALARM  false   2024-06-20 18:14:04.735365  2024-06-20 18:14:01.509219             3        35.32

Avoid Detect RDICCM Defect

Description

In this scenario, a CFM service with MepID 10 is configured in DUT0. But, in DUT1, a CFM service with no remote MepID is configured. This causes DUT1 to detect a defect and activate its RDI flag, which also causes DUT0 to receive CFM datagrams with the RDI flag in UP. Consequently, RDICCM defects are detected. However, the CFM service can be configured so that it doesn’t detect defects under a certain priority level. Since the RDICCM defect has a priority of 1, by configuring a minimum detection level of 2 in DUT0, RDICCM defects are not detected.

Scenario

Step 1: Set the following configuration in DUT0:

set interfaces ethernet eth0 address 10.0.0.1/24

Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 address 10.0.0.2/24

Step 3: Set the following configuration in DUT0:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 alarm TEST_ALARM
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 10 rmep 20
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm min-notification-level 2

Step 4: Set the following configuration in DUT1:

set system alarm TEST_ALARM initial-state true
set service cfm domain TEST_DOMAIN level 6
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm delay 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE alarm reset 2500
set service cfm domain TEST_DOMAIN service TEST_SERVICE sender-id chassis
set service cfm domain TEST_DOMAIN service TEST_SERVICE continuity-check interval 1s
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 interface eth0
set service cfm domain TEST_DOMAIN service TEST_SERVICE mep 20 alarm TEST_ALARM

Note

After a few seconds, the CFM service of DUT0 should not detect any defects.

Step 5: Run command service cfm mep show at DUT0 and check if output matches the following regular expressions:

RDI bit: down
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefNone
\s+20\s+osdx\s+([a-fA-F0-9]{2}:){5}[a-fA-F0-9]{2}\s+ok\s+\d+\s+up\s+up\s+up
Show output
================
=== MEP Info ===
================

MEPID: 10
Type: down
Network: eth0
MAC address: de:ad:be:ef:6c:10
Domain: TEST_DOMAIN at level 6
Service: TEST_SERVICE with no vlan association
RDI bit: down
Port state: up
Interface state: up
enableRMEPdefect: enabled
FNG state: reset
FNG current defect: DefNone
FNG last reported defect: DefNone
Last sent sequence number: 11
Out-of-sequence CCMs: 0
Remote MEPs: 1

---------------------------------------------------------------------------------------------------------
rMepID  SenderID     MAC-address     Status  LastSeqNum  RDI  Port  Interface           LastTime
---------------------------------------------------------------------------------------------------------
    20      osdx  de:ad:be:ef:6c:20      ok          10   up    up         up  2024-06-20 18:14:17.172670

Step 6: Run command system alarm TEST_ALARM show at DUT0 and check if output contains the following tokens:

false
Show output
---------------------------------------------------------------------------------------
  Alarm     Status           Toggled            Prev-toggled  Toggle-count  Time up (%)
---------------------------------------------------------------------------------------
TEST_ALARM  false   2024-06-20 18:14:15.743057                           1         0.61