CFM (OAM IEEE 802.

1ag)
Connectivity Fault Management

Module Version V2.0

Perquisites

Prior to this configuration, end-user need to

be familiar with the following modules:

Ethernet Frame Structure

802.1p/q
CFM Theory
Switch Configuration
Interfaces Configuration

Proprietary and Confidential

Agenda
CFM: Why?

Preliminary configuration
Setup Review
Configuration Flow
Configuration Review
Manual PING
Manual Linktrace
Automatic Linktrace

Proprietary and Confidential

CFM: WHY ?
By definition, L3 IP or L2 ETH are Connection-less networks

In connection-less networks we are blind unable to determine packet path

or latency

This makes troubleshooting and maintenance a harder task

Solution: we need to convert our Connection-less network into a

Connection-Oriented network

I
N

I
N

Connection-Less
4

O
U

O
U

Connection-Oriented
Proprietary and Confidential

CFM: WHY ?

Connection-Oriented networks (ATM, IP/MPLS) enable administrators setting a

pre-defined packet path, reserving BW per service, faster event detection and
thus effective troubleshooting & maintenance

Such technologies are too expensive and sometimes not feasible for Mobile
Operators / Mobile Backhaul solutions

Solution: use a cheaper technology with enhanced features:

Ethernet Core + Operations, Administration & Maintenance support (CFM)

CFM enables L3 operations

such as Traceroute and
PING with a simpler ETH
infrastructure
Connection-Oriented
5

Proprietary and Confidential

Preliminary Configuration

1. Make sure you define the required VLAN IDs in the Switch DB prior to OAM
configuration
2. Prepare a Network Design Map with required configuration
(MIP / MEP / IDs / MAC per device.)
4. Make sure IP-10 Interfaces are configured according to your Network Criteria
(Trunk / Port VID Membership ).
5. Every CFM interface (including Radio) must be aware of the required VIDs
(Port membership)
6. CFM requires physical connection, therefore make sure your interfaces are
enabled on both sides (DCE and DTE)

Proprietary and Confidential

Setup Review (MAIDs):

Domain 1 Services:

Port

3
Port

D1S1:
MEP 1 to MEP 2, Level 3, VLAN 1000
D1S2:
MEP 3 to MEP 4, Level 3, VLAN 2000

8
Port 8

Port 3

4
Dom
ain
1

Domain 2 Services:

D2S2:
MEP 5 to MEP 6, Level 2, VLAN 1000
MEP

Dom
ain
2

MIP
7

Proprietary and Confidential

CFM Configuration Flow:

1

Create VLANs in Switch DB

Assign VID membership per port

Create Domains and Services

Assign MIPs

You may use Advanced features to

troubleshoot a L2 problem

All Steps must be configured on both IP-10s

Make sure you follow the same syntax

Proprietary and Confidential

Configuration

Switch Configuration Mode and VIDs

10

Proprietary and Confidential

Switch Configuration Port Configuration

11

Proprietary and Confidential

Creating MAIDs
Click on the Add button to add domains
(use the setup diagram as a reference)
:You will need to specify
1.Domain Name
2.Level (1 to 7)
3.Association Name
4.VLAN ID

12

Proprietary and Confidential

Creating MAIDs
Create the domains as depicted in the setup diagram on both IDUs
Settings must be unique and identical

13

Proprietary and Confidential

Domains defined
You should see the following status on your MAID list page (on both IDUs):
If you point your cursor to the No MEPs indication LED, you will be notified that MEPs
need to created as well

14

Proprietary and Confidential

Defining MEPs
Click on the ADD button to add a local MEP on both IDUs
Continue to next slide to observe how

15

Proprietary and Confidential

Defining MEPs
Port #3
MEP ID: 1

Port #3
MEP ID: 2

16

Proprietary and Confidential

RIGHT IP-10

Remote MEPs not defined yet

17

Proprietary and Confidential

RIGHT IP-10

LEFT IP-10

Enable CCM on both IDUs

18

Proprietary and Confidential

CCM enabled > Remote MEP is detected

As you can see, CCM enables auto-learning, hence both MEPs discover each other
(MAC and remote MEP ID are now known)
New alarms indicate that process of creating the remote MEP is not fully complete
19

Proprietary and Confidential

Creating Remote MEPs

Click on the Add button to add a remote MEP on every IDU

20

Proprietary and Confidential

Creating Remote MEPs

Port #3
Local MEP ID: 1
Remote MEP: 2

21

Port #3
Local MEP ID: 2
Remote MEP: 1

Proprietary and Confidential

Service #1 (D1S1) is ready for monitoring!

Click on the PING button to check connectivity to Remote interface

(results on next slide)
22

Proprietary and Confidential

PING results (MEP1 to MEP2)

D1S1

23

Proprietary and Confidential

D1S2 Creating another service

We shall create a new service (S2) using the same Domain (D1) (hence- same level)
To separate the 2 services, we shall assign a new VLAN

D1S2

MEP1
MEP 3
MEP 4
Do
m

New Domain: D1S2

ain

MEP 3 to MEP 4
Level 3
VLAN 2000
The new service D1S2 will
monitor the Radio ports
24

Proprietary and Confidential

MEP 2

D1S2 Creating another service

Using the MAID list, add the new service on both IDUs:

D1S

MEP 3
MEP 4
Do
ma
in 1

25

Proprietary and Confidential

D1S2 Creating Local MEPs

Please note - Radio port MEP should be defined as a Downstream MEP

D1S

MEP 3
MEP 4
Do
ma
in 1

26

Proprietary and Confidential

D1S2 Enable CCM on both IDUs

D1S

MEP 3
MEP 4
Do
ma
in 1

27

Proprietary and Confidential

D1S2 Add Remote MEPs on both IDUs

D1S

MEP 3
MEP 4
Do
ma
in 1

28

Proprietary and Confidential

D1S2 Service is now ready for monitoring

29

Proprietary and Confidential

D2S2 another service on another Domain

Port

3
Port

Port 8
Port 3

Dom
ain
1

D2S2

5
6
Dom
ain
2

30

Proprietary and Confidential

D2S2 another service on another Domain

31

Proprietary and Confidential

Adding Local MEPs

Port
3
Radio
s
Port 3
Dom
ain

Local MEP 5
Remote MEP 6
Do

32

ma

in 2

Local MEP 6
Remote MEP 5

Proprietary and Confidential

Enabling CCMsAdding Remote MEPs

Once you complete these tasks, your 3rd service is ready for monitoring

33

Proprietary and Confidential

Adding MIPs to enhance Monitoring

The MIPs can be regarded as
Service-free test-points
MIPs provide more segments
regardless of VLANs and
Services
More test-point
More L2 capabilities!

Port

Dom
ain
1

We shall add a MIP point on

every Radio interface

Make sure you set the MIP

level according to the level
of the Parent domain
34

Port 8

Dom
ain
2

Proprietary and Confidential

Lev
el

Lev
el

Adding MIPs to enhance Monitoring

In the MEP & MIP list, we can see the switch ports and there
MACs:
In our example, we need to add a MIP on the Radio port
Therefore, we shall expand the Radio port to configure the
MIP
Add MIPs on both radio ports (both IDUs)

35

Proprietary and Confidential

Adding MIPs to enhance Monitoring

Please make a note of the Radio MAC address of each IDU we shall need it later
36

Proprietary and Confidential

MAC addresses of participating interfaces

00:0A:25:01:8F:AD
00:0A:25:56:27:AC

00:0A:25:56:27:C6

00:0A:25:56:27:C2

Please note the above MACs are an example of given setup

37

Proprietary and Confidential

Manual PING | Manual Link Trace | Automatic Link Trace

Manual PING
To PING from MEP 1 to MEP 2, you will need to set the following parameters:
Remote interface MAC
Level
VLAN
Successful PING requires setting the correct path

39

Proprietary and Confidential

Manual Linktrace
To trace an interface , you will need to set the following parameters:
Remote interface MAC
Level
VLAN
Successful Trace requires setting the correct path

Results on next slide

40

Proprietary and Confidential

Manual Linktrace Results

FDB
MIP informing us that it
received the LTM (link race
message), it is not who we
are looking for but it knows
how to reach the target
interface
We have traced 2 MIPs (on
every Radio port)
Eventually we traced MEP 1
(HIT)

41

Proprietary and Confidential

Automatic Linktrace
To enable Auto Linktrace select the checkbox next to the target Remote MEP
and then click ADD SELECTED

42

Proprietary and Confidential

Automatic Linktrace
Click Linktrace SELECTED

43

Proprietary and Confidential

Thank You !
training.ceragon.com

44