All rights reserved.

Passing on and copying of this

document, use and communication of its contents not
permitted without written authorization from Alcatel-Lucent.

Date
152x CLIP CFM User Guide
20091020
User Guide
152x CLIP
IEEE 802.1ag CFM and ITU-T Y.1731 ETH-OAM

1/13
permitted without written authorization from Alcatel-Lucent.
document, use and communication of its contents not
All rights reserved. Passing on and copying of this

Status Released

Change Note Not Applicable

All rights reserved. Passing on and copying of this document,

use and communication of its content not permitted without
written authorization from Alcatel-Lucent.

152x CLIP CFM User Guide

1/13
 Table of Contents

1 IEEE 802.1ag CFM and ITU-T Y.1731 ETH-OAM....................................................................... 3

1.1 Introduction........................................................................................................................... 3
1.2 IEEE 802.1ag CFM and ITU-T Y.1731 (ETH-OAM) versus IP SLA ................................................... 3
1.3 Alcatel-Lucent Implementation............................................................................................... 3
1.3.1 Components of CFM/ETH-OAM .................................................................................... 4
1.3.2 Utilities and Tests of IEEE 802.1ag (CFM)..................................................................... 6
1.4 CFM/EHT-OAM Point-to-Point Configuration ............................................................................ 6
1.5 CFM/ETH-OAM Loopback (Ping)............................................................................................... 8
permitted without written authorization from Alcatel-Lucent.

1.6 CFM/ETH-OAM SLA Test and Statistics ..................................................................................... 9

document, use and communication of its contents not
All rights reserved. Passing on and copying of this

1.7 CFM/ETH-OAM SLA Test PM Statistics .................................................................................... 10

1.8 CFM/ETH-OAM CC................................................................................................................. 11
1.9 CFM/EHT-OAM MultiPoint-to-MultiPoint Configuration ........................................................... 12

152x CLIP CFM User Guide

2/13
 1 IEEE 802.1ag CFM and ITU-T Y.1731 ETH-OAM

1.1 Introduction
The IEEE 802.1ag (CFM) standard latest draft as of this writing is D8.0 and it is currently undergoing sponsor ballot. It
should become an approved standard sometime later this year (2007). The ITU-T Y.1731 (ETH-OAM) standard was
approved in July 2006 and it complements the IEEE 802.1ag (CFM) standard with additional fault management and
performance management functions.

A summary of the various fault management (FM) and performance management (PM) functions and the Alcatel-Lucent
software release that supports or will support these functions are shown in the following table:

Function 802.1ag Y.1731 FM PM Release

Loopback/Ping (LB) x x x 5.0
permitted without written authorization from Alcatel-Lucent.

Linktrace (LT) x x x 6.0

document, use and communication of its contents not
All rights reserved. Passing on and copying of this

Continuity Check (CC) x x x 5.1

Remote Defect Indication (RDI) x x x 5.1
Alarm Indication Signal (AIS) x x
Lock Signal (LCK) x x
Test Signal (TST) x x
Automatic Protection Switching (APS) x x
Maintenance Channel (MCC) x
Experimental (EXP) x
Vendor Specific (VSP) x
Frame Loss Measure (LM) x x 5.0
Frame Delay Measure (DM) x x 5.0

1.2 IEEE 802.1ag CFM and ITU-T Y.1731 (ETH-OAM) versus IP

SLA
The IP SLA module originated from a technology known as Service Assurance Agent (SAA) and was developed by Cisco
to measure network performance by using active traffic monitoring between IP end points in a network. The Cisco IP
SLA sends data across the network to measure performance between multiple network locations or across multiple
network paths. It simulates network data and IP services and collects network performance information in real time.
The information collected by IP SLA includes data about latency, jitter, packet loss, and availability.
The IEEE 802.1ag (CFM) and ITU-T Y.1731 (ETH-OAM) is a standards based technology that is used to measure network
performance by using active traffic monitoring between layer 2 Ethernet end points in the network. This technology
sends layer 2 (Ethernet frames) across the network to measure performance between multiple network locations or
across multiple networks paths. It simulates network Layer 2 data and services and collects network performance
information in real time. The information collected by CFM/ETH-OAM includes data about latency, jitter, packet loss
and availability.

1.3 Alcatel-Lucent Implementation

The Alcatel-Lucent equipment supports CFM/ETH-OAM only on 1521CLIP equipment and not on 1531 CLAS equipment.
1531 CLAS equipment is normally not located at a network end point where SLA or performance measurements are
necessary. The 1531 CLAS can be used to manage and operate CRM/ETH-OAM on the 1521CLIP units connected to the
1531 CLAS. The 1521CLIP supports only Maintenance End Points (MEP). Maintenance Intermediate Points (MIP) will be
supported in a future Alcatel-Lucent software release. CFM/ETH-OAM is support in the Alcatel-Lucent equipment only
via the CLI and WebManger. A CFM/ETH-OAM MIB will be supported in a future Alcatel-Lucent software release. No
interoperability testing with other CFM/ETH-OAM equipment has been performed to date. As soon as the standard is
finalized, interoperability testing will be started.

152x CLIP CFM User Guide

3/13
 1.3.1 Components of CFM/ETH-OAM
CFM/ETH-OAM configuration starts with a number of specific components that make up the technology. The
CFM/EHT-OAM objects shown in the following list are hierarchical.

1. Maintenance Domain (MD)

2. Maintenance Association (MA)
3. Maintenance End Point (MEP)

In addition to these components, there are CFM Tests (and test results) CFM Ping (Loopback), CFM Continuity Check,
and CFM PM Statistics.

Their hierarchical nature means that a Maintenance Domain (MD) must be created before one can create a
Maintenance Association (MA). A Maintenance Association (MA) must be created before one can create a Maintenance
End Point (MEP). And finally a Maintenance End Point (MEP) must be created before one can create a CFM Test.

1.3.1.1 Maintenance Domain (MD)

permitted without written authorization from Alcatel-Lucent.

The Alcatel-Lucent equipment supports up to 8 Maintenance Domains (MD) (also called Maintenance Domains). A
document, use and communication of its contents not
All rights reserved. Passing on and copying of this

Maintenance Domain (MD) is an administrative domain for the purpose of managing and administering a network. At
least one Maintenance Domain (MD) must be created first before any other CFM objects can be created. A
Maintenance Domain (MD) must be assigned a name (1 – 22 alpha-numeric characters). There are three different
types of Maintenance Domains (MD) which is useful for defining the hierarchical relationship of domains. Maintenance
Domains (MD) may nest or touch each other, but they can not intersect each other. The three different types of
Maintenance Domains (MD) are:

• Customer
• Service Provider
• Operator

The concept of Maintenance Domains (MD) is important because of the different scopes of management that must be
provided for the three different organizations involved in a Metro Ethernet service. Customers purchase Ethernet
service from Service Providers. Service Providers may use their own network or the networks of other Operators to
provide the connectivity required for the Ethernet service. A diagram that shows the relationship among the three
different types of Maintenance Domains (MD) is shown below.

152x CLIP CFM User Guide

4/13
permitted without written authorization from Alcatel-Lucent.
document, use and communication of its contents not
All rights reserved. Passing on and copying of this

Maintenance Domains (MD) may also be assigned one of eight Maintenance Levels which are:

Maintenance Level Domain

0–2 Operator
3–4 Service Provider
5–7 Customer

The default Maintenance Level is 0 (Operator Domain). These Maintenance Levels are hierarchical in that higher
numbers represent larger Domains. For example, a customer’s network may span one or more Service Providers
networks, and a Service Providers network may consist of one or more Operator Domains.

An example of a CLI command used to create a Maintenance Domain (MD) is:

create cfmmd

1.3.1.2 Maintenance Association (MA)

Since the Alcatel-Lucent CPE units can have more than one Ethernet Virtual Connection (EVC), a Maintenance
Association (MA) is used to link a Maintenance Domain (MD) to an Ethernet Virtual Connection (EVC) on the unit where
CFM is being configured. The Maintenance Association (MA) must be assigned a name (1 – 22 alpha-numeric
characters) and it must specify the name or instance of a Maintenance Domain (MD) and the name or instance of an
EVC.

An example of a CLI command used to create a Maintenance Association (MA) is:

create cfmma

1.3.1.3 Maintenance End Point (MEP)

A Maintenance End Point (MEP) is defined as one CFM measurement point at the edge of a Maintenance Domain (MD)
and it can be used to generate CFM messages such as CFM pings, respond to loopback and link trace messages, and
catalogue continuity-check information received. A Maintenance End Point (MEP) is used to specify a particular UNI,
UNI direction, and Maintenance End Point Tag and link these with a Maintenance Association (MA).

152x CLIP CFM User Guide

5/13
 An example of a CLI command used to create a Maintenance End Point (MEP) is:

create cfmmep

1.3.2 Utilities and Tests of IEEE 802.1ag (CFM)

1.3.2.1 CFM Ping

The CFM ping utility is somewhat similar to an IP ping and it originates a layer 2 “ping” packet from one MEP to an
MEP at another location. The MEP at the other location returns the “ping” packet to the “ping” packet originator.
The ping results show the roundtrip latency associated with the “ping’ packet.

An example of a CLI command used to create a CFM ping is:

permitted without written authorization from Alcatel-Lucent.

cfmping
document, use and communication of its contents not
All rights reserved. Passing on and copying of this

1.3.2.2 CFM SLA Test

A CFM SLA test collects and stores roundtrip latency, jitter and packet loss (and packet loss converted to availability).
The most recent test results can be displayed for the user.

An example of a CLI command used to display a CFM SLA test results is:

show statistics cfmslatest

1.3.2.3 CFM SLA PM Statistics

The CFM SLA PM statistics consists of the current hour and the previous hour of CFM SLA test results. These PM
statistics are identical to the CFM SLA test results except that these PM statistics are kept only for the current hour
and the previous hour.

An example of a CLI command used to display CFM PM statistics is:

show pmstats cfmslatest

1.3.2.4 CFM Continuity Check

The CFM continuity check proactively monitors service connectivity. When continuity check (CC) is configured for a
MEP, then that MEP multicasts periodic heartbeats to it peer MEPs. When the heartbeat packets are not received, a
connectivity fault is indicated and am alarm will be raised.

An example of a CLI command used to display CFM CC is:

show cfmcc

1.4 CFM/EHT-OAM Point-to-Point Configuration

The configuration for CFM-OAM consists of a number of steps that must be carried out in a logic and hierarchal
sequence. The first configuration example will be a simple point-to-point configuration for the equipment shown in
the following diagram:

152x CLIP CFM User Guide

6/13
permitted without written authorization from Alcatel-Lucent.
document, use and communication of its contents not
All rights reserved. Passing on and copying of this

The first configuration example will be for an Ethernet service that exists between Port 1 of CPE 1001 and Port 1 of
CPE 1002. Please note the port numbers and MAC addresses of these ports in the diagram above.

The following variables have been used in this example:

CFM MD = alpha
CFM MA = mass1
CFM MEP = mep1
CFM CC MEP = ccmep1
CFM CC = cctest1
CFM SLA Test = slatest1

The necessary steps in the configuration on CPE 1001 are as follows:

CLI Command Command Description

config cfm admin enable
create cfmmd alpha level 4
create cfmma mass1 mdid alpha evcid evc1
create cfmmep mep1 maid mass1 uniid 1 meptag 1
create cfmccmep ccmep1 maid mass1 meptag 2
create cfmcc cctest1 mepid mep1
create cfmslatest slatest1 mepid mep1 destmac
00:05:7a:02:31:3c
Enable CFM on CPE 1001
Create CFM MD alpha at level 4
Create CFM MA mass1 between CFM MD alpha and EVC ID
evc1
Create CFM MEP mep1 on MA mass1, UNI ID 1, and meptag 1
Create CFM CC MEP ccmep1 on MA mass1 meptag 2
Create CFM CC cctest1 on MEP ID mep1
Create CFM SLA Test slatest1 on MEP ID mep1 to DA MAC
00:05:7a:02:31:3c

Notes:

1. CFM is disabled by default and must be enabled to be active.

2. CFM MD (mass1) level 4 was selected. It could be set to any level, but since the SLA test was designed to
extend from Port 1 on CPE 1001 to Port 1 on CPE 1002, the entire service provider network is covered from
one customer demarcation to another customer demarcation and level 3-4 are reserved for the service
provider network.

152x CLIP CFM User Guide

7/13
 3. CFM MA EVC ID (evc1) was selected because Ethernet Port 1 on CPE 1001 is associated only with EVC ID evc1.
If Ethernet Port 1001 on CPE 1001 had been selected, then it could be associated with either EVC ID evc1 or
evc2. For the purpose of this example, a VLAN ID was not selected, but a VLAN ID could be specified with
this MA.
4. The required CFM MEP parameters include the name of the MEP (mep1), the MA ID (mass1), the UNI ID (1),
and the mepTag (2). The other important parameter for a MEP is the direction (dir). The default direction is
“ingress”; therefore, it was not specified.
5. The activation of CC requires the creation of a CC MEP (ccmep1) and it must be associated with a MA (mass1)
and be given a mepTag (2) that is unique from any other megTags.
6. The CFM CC test (cctest1) must specify a MEP (mep1) from which the CC is originated to all the remote peers
in the MA.
7. The CFM SLA test (slatest1) specifies the originating mepid (mep1) and the remote MAC address
(00:05:7a:02:31:3c) which is located at the remote end of the CFM SLA test.

The necessary steps in the configuration on CPE 1002 are as follows:

CLI Command Command Description

config cfm admin enable Enable CFM on CPE 1001
permitted without written authorization from Alcatel-Lucent.

create cfmmd alpha level 4 Create CFM MD alpha at level 4

document, use and communication of its contents not
All rights reserved. Passing on and copying of this

create cfmma mass1 mdid alpha evcid evc1
create cfmmep mep1 maid mass1 uniid 1 meptag 2
create cfmccmep ccmep1 maid mass1 meptag 1
create cfmcc cctest1 mepid mep1
create cfmslatest slatest1 mepid mep1 destmac
00:05:7a:02:31:44
Create CFM MA mass1 between CFM MD alpha and EVC ID
evc1
Create CFM MEP mep1 on MA mass1, UNI ID 1, and meptag 2
Create CFM CC MEP ccmep1 on MA mass1 meptag 1
Create CFM CC cctest1 on MEP ID mep1
Create CFM SLA Test slatest1 on MEP ID mep1 to DA MAC
00:05:7a:02:31:44

Notes:

1. The configuration on CPE 1002 is identical to the configuration on CPE 1001 except for the following items:
• The unique identification of CFM and CFM CC meptags (1 and 2) can not be duplicated in a MA. CFM
meptag 1 is used by mep1 in MA mass1 on CPE 1001; therefore, meptag 2 is used by mep1 in MA mass1 on
CPE 1002. The same is true for ccmep1 on CPE 1001 and CPE 1002.
• The DA MAC address (00:05:7a:02:31:44) for the remote peer must be changed to point at the correct
remote peer which is the MAC address of Ethernet Port 1 on CPE 1001.

1.5 CFM/ETH-OAM Loopback (Ping)

The CFM/ETH-OAM Loopback (Ping) command “cfmping” is used like an IP ping command to test connectivity from one
MEP to a remote MEP. The following in an example of a CFM ping command that is used to ping from MEP1 on CPE
1001 to MEP1 on CPE 1002 and the output of that command:

1531 CLAS-1M# cpe 1001 cfmping mepid mep1 destMac 00:05:7a:02:31:3c

Enter <Ctrl-c> to abort.

Reply received: bytes=0 rtt=3ms

Reply received: bytes=0 rtt=3ms
Reply received: bytes=0 rtt=3ms
Reply received: bytes=0 rtt=3ms
Reply received: bytes=0 rtt=3ms
Reply received: bytes=0 rtt=3ms
Reply received: bytes=0 rtt=3ms
Reply received: bytes=0 rtt=3ms
Reply received: bytes=0 rtt=3ms
Reply received: bytes=0 rtt=3ms

PDU statistics:
Sent = 10, Received = 10, Lost = 0 (0% loss)
RTT statistics:
Minimum = 3ms, Maximum = 3ms, Average = 3ms

152x CLIP CFM User Guide

8/13
 OK: Action completed.

The output of the command verifies connectivity between the two MEP and measures the round trip time (rtt) for
each of the 10 packets sent and provides some summary statistics for the packets sent.

1.6 CFM/ETH-OAM SLA Test and Statistics

The CFM/ETH-OAM SLA Test parameters and values of the variables can be displayed by using the “show cfmslatest”
command. The output of the CMF SLA test that has been configured for MEP1 on CPE 1001 is shown below:

1531 CLAS-1M cpe 1001 show cfmslaTest slatest1

CPE 1001 CFM SLA Test 2 (slatest1) parameters:

Keyword Description Value

---------------- ---------------------------------------- -----------------
permitted without written authorization from Alcatel-Lucent.
document, use and communication of its contents not

admin Administrative state enable

All rights reserved. Passing on and copying of this

oper Operational state active

timeActive Test runtime 0 days, 00:34:02
mepId MEP ID mep1
destMac Destination MAC address 00:05:7a:02:31:3c
testFreq Test frequency in seconds 300
iter Packet iterations 10
size Packet size 0
freq Packet frequency in msec 1000
timeout Packet timeout in msec 5000
priority VLAN priority 0

This test runs every 300 seconds and 10 packets are sent for each test. The results of the most recent CFM SLA test
can be displayed by using the “show statistics cfmslatest” command. The output of the CMF SLA test statistics that
has been configured for MEP1 on CPE 1001 is shown below:

1531 CLAS-1M# cpe 1001 show statistics cfmslaTest slatest1

CPE 1001 CFM SLA Test 2 (slatest1) statistics:

Keyword Description Value

---------------- ---------------------------------------- --------------------
time Start time of last test iteration 05/23/2007 15:18:44
avail Service availability (%) 100.000

Test values:
testNum Number of tests 1

Packet values:
pktNum Number of packets 10
pktFail Number of failed packets 0
pktLoss Packet loss 0
pktOOS Packets out of sequence 0
pktLate Number of late packets 0

Round trip time values (ms):

rttNum RTT number 10
rttSum RTT sum 27
rttSum2 RTT sum2 75
rttMin RTT minimum 2
rttMax RTT maximum 3
rttAvg RTT Average 2

Jitter values (ms) (SD = source to destination, DS = destination to source):

152x CLIP CFM User Guide

9/13
 interArrJit Interarrival jitter (in/out) 0/ 0
posJitNum Positive jitter number (SD/DS) 0/ 0
posJitSum Positive jitter sum (SD/DS) 0/ 0
posJitSum2 Positive jitter sum2 (SD/DS) 0/ 0
posJitMin Positive jitter minimum (SD/DS) 0/ 0
posJitMax Positive jitter maximum (SD/DS) 0/ 0
negJitNum Negative jitter number (SD/DS) 1/ 1
negJitSum Negative jitter sum (SD/DS) 1/ 1
negJitSum2 Negative jitter sum2 (SD/DS) 1/ 1
negJitMin Negative jitter minimum (SD/DS) 1/ 1
negJitMax Negative jitter maximum (SD/DS) 1/ 1

1.7 CFM/ETH-OAM SLA Test PM Statistics

The CFM/ETH-OAM SLA test data is also stored in PM buckets. The Alcatel-Lucent equipment maintains test results for
the current hour and the previous hour as PM statistics. The command used to display these CFM PM statistics is
permitted without written authorization from Alcatel-Lucent.

“show pmstats cfmslatest”. A sample of the PM statistics is shown below:

document, use and communication of its contents not
All rights reserved. Passing on and copying of this

1531 CLAS-1M# cpe 1001 show pmstats cfmSlaTest slatest1

CPE 1001 CFM SLA Test 2 (slatest1) performance monitoring statistics:

Keyword Description Value

---------------- ---------------------------------------- --------------------
interval Gathering interval (d = discontinuity) 15:03 d
avail Service availability (%) 100.000

Test values:
testNum Number of tests 10

Packet values:
pktNum Number of packets 100
pktFail Number of failed packets 0
pktLoss Packet loss 0
pktOOS Packets out of sequence 0
pktLate Number of late packets 0

Round trip time values (ms):

rttNum RTT number 100
rttSum RTT sum 276
rttSum2 RTT sum2 780
rttMin RTT minimum 2
rttMax RTT maximum 3
rttAvg RTT Average 2

Jitter values (ms) (SD = source to destination, DS = destination to source):

interArrJit Interarrival jitter (in/out) 0/ 0
posJitNum Positive jitter number (SD/DS) 17/ 11
posJitSum Positive jitter sum (SD/DS) 17/ 11
posJitSum2 Positive jitter sum2 (SD/DS) 17/ 11
posJitMin Positive jitter minimum (SD/DS) 1/ 1
posJitMax Positive jitter maximum (SD/DS) 1/ 1
negJitNum Negative jitter number (SD/DS) 15/ 13
negJitSum Negative jitter sum (SD/DS) 15/ 13
negJitSum2 Negative jitter sum2 (SD/DS) 15/ 13
negJitMin Negative jitter minimum (SD/DS) 1/ 1
negJitMax Negative jitter maximum (SD/DS) 1/ 1

The Alcatel-Lucent equipment also supports statistics for each MEP. The command used to display the statistics for a
MEP is “show statistics cfmmep”. A sample of MEP statistics for mep1 on CPE 1001 is shown below:

1531 CLAS-1M cpe 1001 show statistics cfmmep mep1

152x CLIP CFM User Guide

10/13
 CPE 1001 CFM MEP 1 (mep1) statistics:

Keyword Description Value

---------------- ---------------------------------------- -----------------
lbMsgOut cfmPing Tx message count 71
lbRplyIn cfmPing Rx reply count 50
lbRplyOutOfOrder cfmPing Rx reply count out of order msg 0
lbMsgIn cfmPing Rx message count 0
lbRplyOut cfmPing Tx reply count 0
dmMsgOut cfmSlaTest Tx message count 230
dmRplyIn cfmSlaTest Rx reply count 170
dmMsgIn cfmSlaTest Rx message count 170
dmRplyOut cfmSlaTest Tx reply count 170
ccMsgOut cfmCc Tx message count 6634
ccMsgIn cfmCc Rx message count 4981
ccMsgOutOfOrder cfmCc Rx count out of order messages 0
permitted without written authorization from Alcatel-Lucent.
document, use and communication of its contents not
All rights reserved. Passing on and copying of this

1.8 CFM/ETH-OAM CC
The CFM CC test is a heartbeat packet that is sent from a MEP to all the remote peers. If the heartbeat packet fails or
reports an anomaly, then an alarm is raised. The command that is used to display the parameters of a CC test
(cctest1) is shown below:

1531 CLAS-1M(cpe 1001)# show cfmcc cctest1

CPE 1001 CFM CC Test 1 (cctest1) parameters:

Keyword Description Value

---------------- ---------------------------------------- --------------------
admin Administrative state enable
oper Operational state active
timeActive Test runtime 0 days, 00:52:07
mepId MEP ID 1 (mep1)
mcastMac Multicast MAC address 01:80:c2:00:00:34
fltAlmTim Fault alarm soak time 5000
fltClrTim Fault clear soak time 10000
fltAlmMin Alarm fault minimum rdi
fltStatus Fault status 0x0002-macstatus
almStatus Alarm status 0x0002-macstatus

CPE CFM CC MEP Status database:

Instance type mepId oper macAddress rdi

-------- ----- -------------------- ---------- ----------------- -----
1001/1 ccMEP 1 (ccmep1) active 00:05:7a:02:31:3c false

In addition to a continuity check, this feature also report anomalies between the MEPs. The types of alarms that may
be raised and cleared are:

• RDI – A peer MEP reports loss of connectivity with another peer MEP
• MAC STATUS – A peer MEP that is ingress facing reports that its underlying Ethernet port/interface is down
• REMOTE MEP – A local MEP reports loss of connectivity with a peer MEP
• ERROR – A protocol error has occurred (e.g., unexpected peer MEP, etc.)
• CROSS-CONNECT – A MEP has been detected in a different service (i.e., a different MD or MA)

The status of a CC MEP can be displayed using the “show cfmccmepstatus” command. A sample output from this
command is shown below:

1531 CLAS-1M cpe 1001 show cfmccmepstatus 1

152x CLIP CFM User Guide

11/13
 CPE 1001 CFM CC MEP Status 1 database:

Keyword Description Value

---------------- ---------------------------------------- --------------------

sessionId CC session ID 1 (cctest1)

type Local MEP or remote CC MEP ccMEP
mepId MEP ID 1 (ccmep1)
oper Operational state active
timeActive Test runtime 0 days, 01:04:49
macAddress MAC address 00:05:7a:02:31:3c
rdi RDI status false
port Port status blocked
if Interface status down
permitted without written authorization from Alcatel-Lucent.
document, use and communication of its contents not

1.9 CFM/EHT-OAM MultiPoint-to-MultiPoint Configuration

All rights reserved. Passing on and copying of this

For multipoint-to-multipoint configurations, the number of paths through the network increases dramatically. The
formula used to calculate the number of possible paths through the network with N end points is (N * N-1)/2. To set
up CFM SLA tests for all of the possible paths would yield an unwieldy situation. Therefore, only a subset of all the
possible CFM SLA tests is practical.

Most ELAN (multipoint-to-multipoint) services have a single headquarters location. It is practical to set up CFM SLA
tests from the headquarters hub location (MEP) to all or at least a majority of the remote locations (MEP) and use this
configuration as a representative sample of all of the possible paths in the network. If all the locations are peers and
there is no headquarters location, then the network operator must select one of the locations to be the root
(headquarters) location for setting up with CFM SLA tests.

Please note that the CFM CC function will provide connectivity and alarms for all of the paths through the networks as
long as a CC MEP has been configured for each location.

152x CLIP CFM User Guide

12/13