CTR 8500-8300 3.0 ECFM Config July2015 260-668256-001

CTR 8300/8500 CONFIGURATION
EFCM
Version 3.0
260-668256-001
Copyright & Terms of Use
July 2015
This documentation incorporates features and functions provided with CTR 8540 and CTR 8300 for software
release 3.0
Copyright © 2015 by Aviat Networks, Inc.
All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a
retrieval system, or translated into any language or computer language, in any form or by any means, elec-
tronic, magnetic, optical, chemical, manual or otherwise, without the prior written permission of Aviat Net-
works Inc. To request permission, contact techpubs@aviatnet.com.
Warranty
Aviat Networks makes no representation or warranties with respect to the contents hereof and specifically dis-
claims any implied warranties or merchantability or fitness for any particular purpose. Further, Aviat Net-
works reserves the right to revise this publication and to make changes from time to time in the content
hereof without obligation of Aviat Networks to notify any person of such revision or changes.
Safety Recommendations
The following safety recommendations must be considered to avoid injuries to persons and/or damage to the
equipment:
1. Installation and Service Personnel: Installation and service must be carried out by authorized personnel who
have the technical training and experience necessary to be aware of any hazardous operations during install-
ation and service, and of measures to avoid any danger to themselves, to any other personnel, and to the equip-
ment.
2. Access to the Equipment: Access to the equipment in use must be restricted to service personnel only.
3. Safety Norms: Recommended safety norms are detailed in the Health and Safety sections of this guide.
Local safety regulations must be used if mandatory. Safety instructions in this guide should be used in addi-
tion to the local safety regulations. In the case of conflict between safety instructions stated in this guide and
those indicated in local regulations, mandatory local norms will prevail. Should local regulations not be man-
datory, then the safety norms in this guide will prevail.
4. Service Personnel Skill: Service personnel must have received adequate technical training on tele-
communications and in particular on the equipment this guide refers to.
Trademarks
All trademarks are the property of their respective owners.
End User License Agreement and Open Source
By using this product you agree to the terms of the CTR 8540 End User License Agreement; to view this, log
into a CTR 8540 or CTR 8300 using the CLI command window and enter the CLI command “show EULA”.
The CTR 8540 and CTR 8300 use free and open source software components, which can be viewed by using
the CLI command “show system acknowledgments”. This command also details the licenses associated with
each component and describes the methods available to acquire the open source software.
260-668256-001 JULY 2015 I

ECFM CONFIGURATION FOR CTR 8300 AND 8500
Aviat Networks Technical & Sales

Support
Technical Service and Support
For customer service and technical support, contact one of the regional Technical Help Desks listed below, or
for 24/7 (all day, every day of the year) there is the Global Technical Help Desk (GTHD). A call will be answered
by GTHD support staff who will resolve the issue, if possible, or quickly pass the call to the appropriate TAC
engineer for resolution. Contact information is available below or on the Aviat Networks web site.
Global Technical Help Desk
The GTHD number is: +1-210-526-6345, or toll free 1-800-227-8332 within USA
For 24/7 access you will need your Support Assurance PIN. Without a PIN you will still receive support, but the
support process will require an additional screening step. After-hours calls to Paris are routed to the GTHD,
with the existing number left in place during business hours.
Americas Technical Help Desk EMEA Technical Help Desk Asia Pacific Technical Help Desk
Aviat Networks Aviat Networks Aviat Networks
5200 Great America Parkway 4 Bell Drive Bldg 10, Units A&B
Santa Clara CA 95054 Hamilton International Technology Philexcel Industrial Park
U.S.A. Park M. Roxas Hi-way
Blantyre, Glasgow, Scotland Clark Freeport Zone
G72 0FB Philippines 2023
United Kingdom
Toll Free (Canada/USA): 800 227 Phone: Phone: +63 45 599 5192
8332 Hamilton: +44 (0) 1698 717 230 Fax: +63 45 599 5196
Phone: 210 561 7400 Paris: +33 (0) 1 77 31 00 33
Fax: 210 561 7399 Fax: +44 (0) 1698 717 204
Cus- Cus- CustomerCare.Asia@aviatnet.com
tomerCare.Americas@aviatnet.com tomerCare.EMEA@aviatnet.com
Sales and Sales Support

Contact one of the Aviat Networks headquarters, or find your regional sales office on the Aviat Networks web
site.
Corporate Headquarters, California, USA International Headquarters , Singapore
Aviat Networks, Inc. Aviat Networks(S) Pte. Ltd.
5200 Great America Parkway 17, Changi Business Park Central 1
Santa Clara CA 95054 Honeywell Building, #04-01
U.S.A. Singapore 486073
Phone: + 408 567 7000 Phone: +65 6496 0900
Fax: + 408 567 7001 Fax: + 65 6496 0999
Sales Inquiries: +1-321-674-4252
II AVIAT NETWORKS
Product Compliance Notes

CTR 8540, CTR 8312, and CTR 8311 have been tested for and meet EMC Directive 2004/108/EC. The equipment
was tested using screened cable; if any other type of cable is used, it may violate compliance.
CTR 8540, CTR 8312, and CTR 8311 are Class A products. In a domestic environment these products may
cause radio interference in which case the user may be required to take adequate measures. This equipment
is intended to be used exclusively in telecommunications centers.
At CT R s of tw ar e r el eas e 3 . 0 , op er ati on of IRU 6 0 0 i s n ot s u p p or ted .
At CT R s of tw ar e r el eas e 3 . 0 , op er ati on of ODU 6 0 0 or ODU 3 0 0 h p on ANSI f r eq u en c y b an d s
i s n ot s u p p or ted .
At CT R s of tw ar e r el eas e 3 . 0 , op er ati on of ODU 6 0 0 on th e l i c en s e- f r ee 5 . 8 GHz b an d i s n ot
s u p p or ted .
International Use of 5.8GHz

ODU 600 or IRU 600 with CTR 8540, CTR 8312, or CTR 8311 on the 5.8 GHz license-free band do not employ
DFS, and as such the equipment cannot be deployed within Europe or any country where DFS is a regulatory
requirement for protection of radars.
WEEE Directive
In accordance with the WEEE Directive (2002/96/EC), CTR 8540, CTR 8312, and CTR 8311 are marked with the
following symbol:
This symbol indicates that this equipment should be collected separately for the purposes of recovery and/or
recycling.
For information about collection and recycling of Aviat Networks equipment please contact your local Aviat
Networks sales office. If you purchased your product via a distributor please contact the distributor for inform-
ation regarding collection and recovery/recycling.
More information on the WEEE Directive is available at our website:
http://www.aviatnetworks.com/products/compliance/weee/.
(WEEE is the acronym for Waste Electrical and Electronic Equipment)
RoHS Directive
CTR 8540, CTR 8312, and CTR 8311 meet the requirements of ROHS directive 2011/65/EU.
260-668256-001 JULY 2015 III

Declaration of Conformity, R&TTE Directive, 1999/5/EC

The reference to CTR in this declaration denotes intended use of the CTR 8540, CTR 8312, or CTR 8311, with
one or more of the following Aviat Networks ODUs: ODU 600, ODU 600sp, ODU 300hp.
IV AVIAT NETWORKS
The CTR 8540, CTR 8312, or CTR 8311 with an ODU 600, ODU 600sp, or ODU 300hp radio is classified under the
R&TTE Directive 99/5/EC as a class 2.8 radio (microwave fixed link) product.
Point-to-point radio relay equipment is intended to be used for:
- Interconnecting private and public networks.
- Interconnecting mobile base stations back to the PSTN point of presence (POP).
For details of where the equipment is intended to be used, see the country matrix below.
- AVIAT NETWORKS intends to market this equipment where a cross (X) is shown in the table below.
- The information contained in this table has been gathered from the relevant government authorities and
relates only to European countries participating in the R&TTE directive.
It s h ou l d b e n oted th at a l i c en s e to op er ate th i s eq u i p men t i s l i kel y to b e n ec es s ar y, an d
th e ap p r op r i ate r eg u l ator y ad mi n i s tr ati on s h ou l d b e c on tac ted .
260-668256-001 JULY 2015 V

VI AVIAT NETWORKS
ECFM Configuration Table of Contents

Copyright & Terms of Use i
Aviat Networks Technical & Sales Support ii
Product Compliance Notes iii
International Use of 5.8GHz iii
WEEE Directive iii
RoHS Directive iii
Declaration of Conformity, R&TTE Directive, 1999/5/EC iv
ECFM Configuration Table of Contents vii
CHAPTER 1. INTRODUCTION TO ECFM 1

Purpose and Scope 1
Acronyms 1
IEEE 802.1ag and ITU-T Y.1731 Terminology Mapping 3
References 3
Document Conventions 3
General Configurations 3
CLI Configurations 3
ECFM Protocol Description 5
Ethernet CFM 5
Maintenance Domain 6
Maintenance Association / Service Instance 6
Maintenance Point 7
MEP Functions 8
MHF (MIP Half Function) Functions 8
CFM Features 8
Fault Management 8
CHAPTER 2. CONFIGURING ECFM 11

Configuration Guidelines 11
Default Configurations 12
Configuring the ECFM Capabilities 12
Configuring Maintenance Domain 12
Configuring Maintenance Association 13
260-668256-001 JULY 2015 VII

Configuring Maintenance End Points 14

Configuring Maintenance Intermediate Points 15
Associating a Set of VLANs to a Primary VLAN 19
Enabling Ethernet CFM 20
Enabling ECFM on an Interface 20
Enabling Ethernet Y.1731 21
Enabling Y.1731 on an Interface 21
Enabling and Disabling Ethernet CCM Offload 22
Configuring and Enabling Continuity Check Messages 22
Enabling Crosscheck between Configured Remote MEPs 23
Configuring and Enabling LoopBack Messages 24
Configuring and Enabling Linktrace Messages 26
Configuring and Enabling Alarm Indication Signal Messages 27
Setting OUI (Organizational Unit Identifier) 28
Enabling LLC Encapsulation on interface 29
Displaying Ethernet CFM Entities 29
CLI Configurations 29
Displaying Maintenance Domain 30
Displaying Maintenance Association 30
Displaying Maintenance Points configured 30
CHAPTER 3. FLOW BASED CONFIGURATION 33

Creating Interfaces 33
Creating VLAN 33
Enabling ECFM, Traceroute Caching and MIP CCM Database 34
Configuring Maintenance Domain, Service and MEPs 34
Enabling CCM transmission 35
Configuring MIP 35
Verifying Configured MPs (MEP and MIP) 35
Checking for CCM Errors 36
Checking for Configured Remote Entities in the Network 37
Generating CCM Errors 38
Verifying and Isolating Fault 39
Bridge Up Interface 40
Checking for CCM Errors 40
Verifying and Isolating Fault 41
Enabling Y1731 42
Initiating Frame Delay Measurement 42
VIII AVIAT NETWORKS

Initiating Frame Loss Measurement 43

Initiating Test Message 44
Initiating Availability Measurement 44
260-668256-001 JULY 2015 IX

Chapter 1. Introduction to ECFM

Aviat Networks ECFM (Ethernet Connectivity Fault Management) specifies the protocol entities
within the architecture of Virtual Bridged LAN (Local Area Network) that provide the cap-
abilities for detecting, verifying and isolating connectivity failures in the Virtual Bridged LAN.
This is done via continuity check, loopback, and trace protocols for providing complete 802.1ag
functionality. Performance monitoring is done using loss, delay, and throughput measurement
functions.
Purpose and Scope

This document describes the CLI (Command Line Interface) configurations of Aviat Networks
ECFM to detect isolate and verify the faults in connectivity in the ECFM managed links.
The reader is expected to have a basic knowledge of the protocol as a pre-requisite, and to be
familiar with CTR 8300 and 8500.
Acronyms
Table 1-1. Acronyms used in this document
Acronym Expansion
AIS Alarm Indication Signal
bps Bits per second
CBP Customer Bridge Port
CCM Continuity Check Message
CFM Connectivity Fault Management
CFM PDU CFM Protocol Data Unit
CLI Command Line Interface
CNP Customer Network Port
DMM Delay Measurement Message
DMR Delay Measurement Reply
ECFM Ethernet Connectivity Fault Management
ETH-TH Ethernet Throughput Measurement
EXM Experimental OAM Message
EXP Experimental OAM function
EXR Experimental OAM Reply
FL Frame Loss
ICC ITU Carrier Code
260-668256-001 JULY 2015 1

CHAPTER 1. INTRODUCTION TO ECFM
IPDV Inter-Packet Delay Variation

LAN Local Area Network
LBM LoopBack Message
LBR LoopBack Reply
LCK Locked
LMM Loss Measurement Message
LMR Loss Measurement Reply
LTM LinkTrace Message
LTR LinkTrace Reply
MA Maintenance Association
MAC Media Access Control
MAID Maintenance Association Identifier
MCC Maintenance Communication Channel
MD Maintenance Domain
ME Maintenance Entity
MEG Maintenance Entity Group
MEP Maintenance End Point
MEPID Maintenance End Point Identifier
MHF MIP Half Function
MI Multiple Instance
MIP Maintenance Intermediate Point
MPLS Multi Protocol Label Switching
MPLS-TP Multi Protocol Label Switching –Transport Profile
MSTP Multiple Spanning Tree Protocol
OAM Operations, Administration and Maintenance
PDV Packet Delay Variation
PIP Provider Instance Port
PNP Provider Network Port
pps Packets per second
SNMP Simple Network Management Protocol
TST Test
UMC Unique MEG ID Code
VLAN Virtual LAN
VSM Vendor Specific OAM Message
VSP Vendor Specific OAM
VSR Vendor Specific OAM Reply
2 AVIAT NETWORKS
IEEE 802.1ag and ITU-T Y.1731 Terminology Mapping

Table 1-2. Terminology Mapping
ITU-T Y.1731 terminology IEEE 802.1ag terminology
Maintenance Entity (ME) Maintenance Association (MA)
Maintenance Entity Group (MEG) Maintenance Domain (MD)
Maintenance Entity Group End Point (MEP) Maintenance Association End Point
(MEP)
Maintenance Entity Group Intermediate Point Maintenance Domain Intermediate
(MIP) Point (MIP)
Maintenance Entity Group Identifier (MEG ID) Maintenance Association Identifier
(MA ID)
MEG Level MD Level
References
l CTR 8500/8300 CLI User Manual
l IEEE Standard P802.1ag/D7.0 – Draft Standard for Virtual Bridged Local and
Metropolitan Area Network.
l ITU-T Recommendation Y.1731 (05/2006) – Draft for OAM functions and
mechanisms for Ethernet based networks.
Document Conventions
Table 1-3. Conventions Used in this Document
Convention Usage
Code text CLI (Command Line Interface) Com-
mands
Code Italics User Inputs to Command
Blue code CLI Command output
Red code Output of the configured value
General Configurations
CLI Configurations
This table lists the access and exit methods to the various CLI configuration modes.
Table 1-4. General Configurations
260-668256-001 JULY 2015 3

CHAPTER 1. INTRODUCTION TO ECFM
Command Mode Access Method Prompt Exit method

User EXEC This is the initial mode aos> The logout method is used.
to start a session.
Privileged EXEC Use the enable com- aos# Use the command disable to
mand to enter the Priv- return from the Privileged EXEC
ileged EXEC mode. mode to User EXEC mode, the
disable command is used.
Global Con- Enter Privileged EXEC aos(config)# Use the command exit to log
figuration mode and use the com- out of the Global Configuration
mand configure Mode, and the command end to
terminal to enter log out of the Privileged EXEC
the Global Con- mode.
figuration Mode.
Interface Con- In Global Configuration aos(config-if)# Use the command exit to log
figuration Mode, use the com- out of the Global Configuration
mand command Mode, and the command end to
interface <inter- log out of the Privileged EXEC
face-type><in- mode.
terface-id>to enter
the Interface Con-
figuration Mode.
ECFM con- The global con- aos(config- Use the command exit to
figuration figuration mode com- ether-ecfm)# return to the Global Con-
mand ethernet cfm figuration Mode, and the com-
domain is used to mand end to return tothe
enter the ECFM con- Privileged EXEC mode.
figuration mode. In
this mode, user can
configure various para-
meters applicable to
this domain.
ECFM MEP con- The interface con- aos(config- Use the command exit to
figuration figuration mode com- ether-mep)# return to the Interface Mode, and
mand ethernet cfm the command end to log out
mep is used to enter return to the Privileged EXEC
the ECFM MEP con- mode.
figuration mode. In
this mode, user can
configure various para-
meters applicable to
this MEP.
4 AVIAT NETWORKS
ECFM Protocol Description

This section describes Aviat Networks ECFM and provides an overview of its features, such as
MD (Maintenance Domain), MA (Maintenance Association), Maintenance Point and CFM (Con-
nectivity Fault Management) messages.
Ethernet CFM
Aviat Networks ECFM provides capabilities useful for detecting, verifying, isolating connectivity
failures and performance monitoring in Virtual Bridged LANs. The fault detection, isolation and
verification are done through continuity check, loopback and linktrace protocols. Performance
monitoring is done using LM and DM functions. These capabilities can be used in networks
operated by multiple independent organizations, each with restricted access to each other’s
equipment.
In general, the network administrator is informed about the failure in the connection, based on
the reception of CCMs (Continuity Check Messages). The administrator can then initiate loop-
back or linktrace accordingly to determine and isolate the fault condition.
Aviat Networks ECFM also provides performance monitoring functions for measurement of vari-
ous performance parameters in Ethernet point-to-point connections. It also supports meas-
urement of frame loss ratio, frame delay and frame delay variation performance parameters.
The CFM information is conveyed in protocol frames called CFM PDUs (CFM Protocol Data
Units). The CFM PDUs contain the appropriate control and status information used to detect,
verify, and isolate faults. It also contains information for path discovery in CFM-enabled links.
The CFM PDUs are processed, forwarded or discarded by the entities configured in the Bridge
port, based on the MD (Maintenance Domain) level to which that entity belongs.
Overall, the CFM information:
l Defines Maintenance Domains, Maintenance Associations, their constituent Main-
tenance Points, and the managed objects required to create and administer them.
l Describes the protocols and procedures used by Maintenance Points to detect and
diagnose connectivity faults within a maintenance domain.
CFM Functions are categorized as follows:
l Fault Detection
l Fault Verification
l Fault Isolation
l Fault Notification
Fault Detection uses Continuity Check Protocol to detect both connectivity failure and unin-
tended connectivity between service instances. Each MEP (Maintenance End Point) periodically
transmits a multicast CCM announcing the identity of the MEP and its MA and tracks the
CCM reception from other MEPs.
Fault Verification is an administrative action, typically performed after fault detection. It uses
Loop Back Protocol to perform Fault Verification. An MEP is ordered to transmit unicast LBM
260-668256-001 JULY 2015 5

message to MEP in an MA, and the receiving MEP replies (if Target MAC (Media Access Con-
trol) Address matches) sends a LBR (Loop Back Reply) message.
Fault Isolation is also an administrative action that uses Link Trace Protocol to isolate the fault
location, in which an MEP is ordered to transmit multicast LTM (Link Trace Message) in an
MA. All the receiving entities, of the same MA, replies to it with unicast LTR (Link Trace Reply)
message and failure in expected LTR reception from an ECFM entity, finally isolates the fault
location.
Fault Notification is achieved by Alarm Indication Signals, which notify and suppress alarms
on fault events, allowing the relevant operators to take appropriate actions.
Maintenance Domain
A Maintenance Domain is the network or the part of the network for which faults in con-
nectivity are managed. A domain is owned and operated by a single entity and defined by a set
of ports internal to it and at its boundary.
Figure 2-1. Maintenance Domain in ECFM

A Maintenance Domain is fully connected internally, that is, an MEP associated with an MD
has connectivity to every other MEP in the MD, in the absence of faults. The purpose of CFM is
to monitor and diagnose the ability of a maintenance domain to meet its operators’ intentions
for connectivity.
Each Maintenance Domain is assigned a unique Maintenance Domain Name and Domain Level
to facilitate the easy identification of administrative responsibility for the Maintenance Domain.
Domains must not intersect, because intersecting indicates the management by more than one
entity, which is not allowed.
Maintenance Association / Service Instance

Administrator while configuring Maintenance Domains defines certain DSAPs (Domain Service
Access Point) to be directly accessed by the customer. Configuring Maintenance End Point on
the defined DSAPs with the same MAID and MD Level, established to verify the integrity of a
single service instance is one Maintenance Association (MA).
6 AVIAT NETWORKS
Figure 2-2. Maintenance Association

This displays one Maintenance Association at the Customer MD Level. Two MEPs are defined
on bridge 1 and 6. The two MEPs together comprise one Maintenance Association.
MA is identified by a Short MA name that is unique in a maintenance domain. MA can only be
associated with a VLAN. A MA is associated with more than one VLAN (Virtual LAN), but dif-
ferent MAs cannot share one VLAN in a single Maintenance Domain (MD).
For Example:
Figure 2-3. Example Maintenance Association

This shows a a service instance from the customer C1 point of view. The customer has four
items of customer equipment attached to the four DSAPs 1-4, by which the operator connects
the four DSAPs to create the service instance that are invisible to the customer.
Maintenance Point
A maintenance point is a demarcation point on an interface (port) that participates in CFM
within a maintenance domain. Maintenance points on device ports act as filters that confine
CFM frames within the bounds of a domain by dropping frames that do not belong to the cor-
rect level. Maintenance Point is either MEP or MHF.
A MEP or MHF, each have two principal SAPs, an Active SAP, through which the CFM Protocol
Data Units (PDUs) are exchanged and a Passive SAP, through which the unprocessed data
frames and CFM PDUs are passed.
A Maintenance Point is UP, if Active SAP is below Passive SAP or DOWN, if Active SAP is above
Passive SAP.
260-668256-001 JULY 2015 7

Figure 2-4. Maintenance Point in ECFM
A MEP is created on the Bridge Port and is associated with exactly one MA. A MEP is identified
by its MEPID (Range 1 - 8191) that is unique in an MA. It inherits the MD Level from the Main-
tenance Domain and the Primary VID from the Maintenance Association.
MEP Functions
MEP is capable of initiating and terminating OAM frames for fault management and per-
formance monitoring.
The following are the MEP functions:
l Periodically transmits multicast or unicast CCMs.
l Transmits LBM, LTM, TST, DMM, LMM, AIS and LCK PDUs and responds to the
LBMs with LBRs, LTMs with LTRs, DMMs with DMRs, and LMMs with LMRs.
l Validates the received PDU.
l Discards the CFM PDUs that are at lower MD level than MEP.
MHF (MIP Half Function) Functions

l Validates the received PDUs.
l Validates the received CCM PDUs, and builds the MIP CCM Database.
l Responds to LBM PDUs with LBR PDUs.
l Responds to LTM PDUs by forwarding them and responding with LTR PDUs.
CFM Features
Fault Management
Fault Management is capability to pro-actively monitor the network for faults and notify the
administrator so that timely action can be taken to ensure availability of the network. Fault
management includes fault detection, fault verification, fault isolation, fault notification and
fault recovery.
8 AVIAT NETWORKS
Continuity Check Protocol

Aviat Networks ECFM uses the CC protocol to detect both connectivity failures and unintended
connectivity between service instances. Each MEP can periodically transmit a multicast CCM
announcing the identity of the MEP and its ME (Maintenance Entity), and track the CCMs
received from the other MEPs. All connectivity faults indicate either misdirected CCMs or the
differences between the CCMs received and the configured expectations of MEP. The state of the
tracked CCMs is available to the operator for examination. Following are the various error con-
ditions that can be tracked through CCMs:
1. Loss of Continuity
2. Mismerge condition
3. Unexpected MEP
4. Unexpected MEG Level
5. Unexpected Period
6. Locally Detected Link Failure
7. Internal Hardware Failure
8. Internal Software Failure
LoopBack Protocol
Aviat Networks ECFM uses the LB Protocol to support the fault verification functionality. Fault
verification is an administrative action typically performed after fault detection. Operator ini-
tiates the unicast LBM (LoopBack Message) transmission from a specific MEP to an MEP/MIP
or multicast LBM transmission to an ME. On reception of LBM, the MP (MEP/MIP) validates
the received LBM and generates the unicast LBR (Loopback Reply), and transmits it to the ori-
ginating MEP. The MEP records the information received in the LBR for examination by the
operator.
Unicast LBM can be used for the following applications:
l To verify bi-directional connectivity of an MEP with an MIP or a peer MEP.
l To perform a bi-directional in-service or out-of-service diagnostics test between a
pair of peer MEPs. This includes verifying bandwidth throughput, detecting bit
errors, and so on.
Multicast LBM can be used for the following application:
l To verify bi-directional connectivity of an MEP with its entire ME.
LinkTrace Protocol
Aviat Networks ECFM uses the LT Protocol to determine the Adjacent Relation Retrieval or for
Fault Localization. Operator initiates the multicast LTM (Link Trace Message) transmission
from a specific MEP to an MEP. On reception of LTM, the MP (MEP/MIP) generates the unicast
LTR (Link Trace Reply), which is transmitted back to the originating MEP. The LTM is also for-
warded to the next MP. The originating MEP accumulates the responses for examination by the
operator.
Alarm Indication Signal

Aviat Networks ECFM uses the AIS (Alarm Indication Signal) to suppress alarms at client-layer
MEP(s), following the detection of a fault/Locked condition/AIS condition at the server-layer
260-668256-001 JULY 2015 9

MEP. Operator can enable or disable the AIS functionality for an MEP, If AIS is enabled and a
fault/Locked Condition/AIS Condition is detected at an MEP, AIS frames will be transmitted to
the client-layer MEPs in the direction opposite to the peer MEP. On reception of the AIS frame,
the client-layer MEP suppresses its fault alarms.
AI S frame can be mul ti cast or uni cast.
10 AVIAT NETWORKS
Chapter 2. Configuring ECFM

The section describes the configuration of ECFM specific features in Aviat Networks CTR 8540.
Configuration Guidelines
This section describes the configuration guidelines for ECFM in SI (Single Instance) mode.
1. The following commands must be executed in the specified sequence to start and
configure the ECFM entities1:
enable
configure terminal
vlan <vlan-id>
ports interface <type> < interface-id >
vlan active
exit
ethernet cfm domain name <domain-name> level
<level-id>
service name <ma-name> [vlan < vlan-id >]
mep crosscheck mpid <mepid> [vlan <vlan-id>]
exit
ethernet cfm enable
ethernet cfm y1731 enable
interface <interface-type><interface-id>
ethernet cfm mep level <level-id> [inward] mpid
<mepid> [vlan <vlan-id>] [active]
exit
ethernet cfm cc level <a,b,c-d> [vlan <a,b,c-d>]
interval {three-hundred-hertz | ten-ms |
hundred-ms | one-sec | ten-sec | one-min | ten-
min}
ethernet cfm cc enable level < a,b,c-d> [vlan <
a,b,c-d>]
exit
The interface type is gigabitethernet or ECFM over radio, and the interface ID needs
to be specified as 0/n, where n is the interface number.
260-668256-001 JULY 2015 11

CHAPTER 2. CONFIGURING ECFM
Default Configurations
Table 2-1. Default Configurations
Feature Default Setting
ECFM System Status Start
ECFM Module Status Disabled
ECFM Port Module Status Based on ECFM
Module Status
ECFM Functionality (CC, LB, LT, DM, LM, TST, AIS, LCK) Disabled
ECFM Entities (MD, MA, MEP, MIP) No Entity Con-
figured
Y.1731 compliant features Disabled
ECFM is operationally disabled, when the switch comes up. When the ECFM is enabled and the
ECFM entities (MD, MA, MEP and MIP) are configured; then CC, LB and LT functionalities can
be started.
By default, Y.1731 features are disabled. It can be enabled only after enabling ECFM. When
Y.1731 is enabled, then TST, AIS, LCK, Frame Loss and Frame Delay functionalities can be star-
ted.
Configuring the ECFM Capabilities

This section describes the configuration of ECFM and Y.1731 entities in SI mode.
Configuring Maintenance Domain

This section describes the configuration of the CFM MD at a particular maintenance level.
CLI Configurations
To configure MD on the bridge:
1. Login to the privileged EXEC mode.
aos> enable
To l ogi n i nto the User Exec mode, use guest as the User-
name and guest123 as the password. To l ogi n to the Pri v-
i l eged mode, use the enabl e command or l ogi n wi th
username as root and password as admi n123.
2. Enter into the global Configuration mode.
aos# configure terminal
3. Configure the domain name and maintenance level.
aos(config)# ethernet cfm domain name
TestDomain1 level 7
aos (config-ether-ecfm)#
12 AVIAT NETWORKS
To delete configured MD:

Enter into the global configuration mode and delete the configured MD.
aos(config)# no ethernet cfm domain name
TestDomain1 level 7
User can configure MD name type/format using
ethernet cfm domain format name level command.
aos(config)# ethernet cfm domain format char-
string name TestDomain2 level 1
User can delete the configured MD name type/format using no ethernet cfm domain format
name level command.
aos(config)# no ethernet cfm domain format char-
string name TestDomain2 level 1
Configuring Maintenance Association

This section describes the configuration of the CFM MA within a particular MD.
The MD must be confi gured pri or to the confi gurati on of
MA.
CLI Configurations
To configure MA:
1. Execute the steps given in the related CLI Configurations for configuring MD
2. Enter into the ECFM configuration mode and configure service at specific VLAN
aos(config-ether-ecfm)# service name CustAssoc1
vlan 101
3. Return to the Global Configuration mode.
aos(config-ether-ecfm)# exit
Users can configure ICC (ITU Carrier Code) and UMC (Unique MEGID Code) using the service
name icc umc command:

icc icc1 umc umc1 vlan 101
User can configure MA name type/format using service format name vlan command.
aos(config-ether-ecfm)# service format primary-
vid vlan 1001
For the configuration of VLAN-UnAware MA(s),
vlan keyword must not be provided with the
command.
To delete configured MA:
Enter into the ECFM configuration mode and delete the service within the MD.
aos(config-ether-ecfm)# no service name
CustAssoc1
User can delete configured MA name type/format using no service format name command.
260-668256-001 JULY 2015 13

aos(config-ether-ecfm)# no service format

primary-vid name 1001
Configuring Maintenance End Points

This section describes the configuration of the MEP.
The MD and MA must be confi gured pri or to the con-
fi gurati on of the MEP.
CLI Configurations
To configure MEP
1. Execute the steps given in the related CLI Configurations for configuring the MA
to which MEP needs to be associated
2. Enter into the ECFM configuration mode and statically define an MEP in a MA-
MEP list within a MA
aos (config-ether-ecfm)# mep crosscheck mpid 5
vlan 101
VLAN-Unaware MEP can be defi ned wi thout speci fyi ng the
vl an parameter i n the command
Make the port 10 as member port of VLAN 101 and configure the VLAN 101 as active
aos(config)# vlan 101
aos(config-vlan)# ports gigabitethernet 0/10
aos(config-vlan)# vlan active
3. Enter into the interface configuration mode
aos (config)# interface gigabitethernet 0/10
4. Configure MEP on the interface in the MD and MA
aos(configure-if)#ethernet cfm mep level 7 mpid
5 vlan 101
I n the command i nward keyword needs to be speci fi ed for
up (i nward) di recti on MEP. Otherwi se MEP wi l l be con-
fi gured as down (outward) di recti on MEP
5. Enable the configured MEP.
aos(config-if)# ethernet cfm mep level 7 mpid 5
vlan 101 active
To delete MEP:
6. Enter into the interface configuration mode and disable the configured MEP
aos(config-if)# no ethernet cfm mep level 7 mpid
5 vlan 101 active
7. Remove the MEP configuration fromm the interface
aos(config-if)# no ethernet cfm mep level 7 mpid
5 vlan 101
8. Return to the global configuration mode
aos(config-if)# exit
14 AVIAT NETWORKS
Port (on whi ch the MEP i s confi gured) and VLAN (VLAN
wi th whi ch MEP i s associ ated) must exi st and must be set
as UP, and ECF M must be enabl ed on the port, for starti ng
VLAN Aware MEP functi onal i ty.
vlan keyword should not be provided with the
command for configuration of VLAN-Unaware MEP.
MEP must be enabl ed expl i ci tl y as MEP i s di sabl ed by
defaul t.
User can enter MEP configuration mode by executing ethernet cfm mep level mpid vlan com-
mand. Where user can configure ccm unicast mac address, client’s mac address for AIS and
LCK, drop eligibility and vlan priority of various CFM PDUs, threshold values for delay and
loss functionality, capabilities, offload status etc.
Configuring Maintenance Intermediate Points

This section describes the configuration of the MIP (Maintenance Intermediate Point) on an
interface.
MIP can be configured on an interface using either of the following two methods:
1. Explicit MIP Creation
2. Implicit MIP Creation
Table 2-2. MIP Creation Criteria
Enumeration Description
none No MIP can be created.
explicit MIP can be created, if there exists an MEP
at next lower MD level on the port.
default MIP can be created on the port.
defer Maintenance Association - Control of MIP
creation criteria is deferred to the cor-
responding variable in the enclosing MD.
Default Domain - Control of MIP creation
criteria is deferred to the corresponding
variable in the Default MD default MHF cri-
teria.
CLI Configurations
Explicit MIP Creation
Explicit MIP can be configured in two ways:
l MIP associated with an MA
l MIP associated with Default Domain
MIP associated with an MA

Pre-requisites:
260-668256-001 JULY 2015 15

1. MA must be configured at same MD level and VLAN at which MIP is to be con-

figured.
2. At least a single Up direction MEP must be configured and associated with MA.
Refer IEEE Standard P802.1ag/D8 Section 22.2.3 (k).
3. MIP creation criteria parameter should be configured for MA. Refer IEEE Standard
P802.1ag/D8 Section 22.2.3 (1,2,3,4).
Configuration steps:
4. Set the default MD level corresponding to the VLAN in Default MD table.
aos(config)# ethernet cfm default-domain vlan
101 level 7
5. Execute the steps given in section CLI Configurations to configure an Up direction
MEP for the level 7 and VLAN 101.
6. Set the MIP creation criteria. Refer MIP Creation Criteria- for the conditions for
each MIP creation criteria. If mip-creation-criteria value of MA is defer, then control
of MIP creation criteria is deferred from MA to MD.
7. Set the MIP creation criteria parameter to default for an MA
aos(config)#ethernet cfm domain name TestDomain1
level 7
aos(config-ether-ecfm)#service name CustAssoc1
vlan 101 mip-creation-criteria default
8. OR
9. Set the MIP creation criteria to defer for an MA and to default for an MD.
TestDomain1 level 7
aos(config-ether-ecfm)# set mip-creation-
criteria default
vlan 101 mip-creation-criteria defer
10. Entert the interface configuration mode and configure an MIP at specified main-
tenance level and VLAN on an interface.
aos(config)# interface gigabitethernet 0/2
aos(config-if)#ethernet cfm mip level 7 vlan 101
MIP associated with Default Domain

Pre-requisites:
1. No MA must be configured at same MD level and VLAN along with an Up dir-
ection MEP.
2. Entry in the Default MD table should be present for the same MD level and VLAN
or Default MD default level should be configured. Refer IEEE Standard P802.1ag/D8
Section 12.14.3.1.3 (b).
3. MIP creation criteria parameter should be configured for Default Domain. Refer
IEEE Standard P802.1ag/D8 Section 22.2.3 (m).
Configuration steps:
Set the parameters such as MD level and MIP creation criteria required for MIP creation for a
VLAN
16 AVIAT NETWORKS
aos(config)# ethernet cfm default-domain vlan

101 level 7 mip-creation-criteria default
active
4. OR set the parameters such as MD level and MIP creation criteria required for MIP
creation at any VLAN.
aos(config)#ethernet cfm default-domain global
level 7 mip-creation-criteria default
active
Implicit MIP Creation

Implicit MIP can be configured when:
l The bridge is initialized.
l MEP is created or deleted on VLAN x on a bridge port.
l A change occurs in the default MD managed object.
l A change occurs in MA associated with VLAN(s).
Managed objects that affect the MIP creation are MA, Default MD, Default Default MD and
MEP.
Table 2-3. Port and VLAN Eligibility Criteria
Condition Eligible Port(s) and VLAN(s)
Bridge initialization Port - Ports that are not a part of port channel.
VLAN(s) - VLAN(s) which are created in the sys-
tem and are associated with some ports.
MEP creation or deletion Port - Port on which the MEP is created and is not
a part of port channel.
VLAN - VLAN with which MEP is associated and is
associated with the port.
MA creation or deletion Port – Ports that are not part of port channel.
VLAN(s) - VLAN(s) with which MA is associated
and is associated with some ports.
Change in Default MD Port - Ports that are not part of port channel.
VLAN - VLAN with which Default MD is asso-
ciated.
Change in Default Default MD Port - Ports that are not a part of port channel.
VLAN(s) - VLAN(s) which are created in the sys-
tem and are associated with some ports.
MIP creation evaluation process

At a particular port, single MIP can be configured for a VLAN at the highest MD level only.
For a particular port p and VLAN x (Refer to the Port and VLAN Eligibility Criteria), MIP cre-
ation is evaluated as follows:
1. Determine eligible MD levels for VLAN x based on:
260-668256-001 JULY 2015 17

2. The MD level of each of the MA that includes VLAN x.

3. The Default MD level corresponding to VLAN x.
4. Determine, from the eligible MD levels, a lowest MD level d which satisfies the fol-
lowing condition:
5. There is no MP configured on the bridge port p and VLAN x at MD level d or MD
level greater than d.
6. Check the MIP creation criteria (refer MIP Creation Criteria-) to determine
whether an MIP is to be created or not.
7. MIP creation criteria are taken from:
8. MA, if there exists an MA that includes VLAN x and has at least one Up MEP con-
figured on some bridge port.
9. MD, if there exists an MA that includes VLAN x, has at least one Up MEP con-
figured on some bridge port and has MIP creation criteria set as defer.
Default MD Level, if an MA that includes VLAN x
does not exist.
10. Default Default MD Level, if an MA that includes VLAN x and the corresponding
Default MD having its MIP creation criteria as defer does not exist.
To create MIP(s) based on trigger 3 (A change that occurs in the Default MD):
1. Enable the implicit MIP evaluation and creation.
aos(config)# ethernet cfm mip dynamic evaluation
2. Set interfaces 1 and 2 as up.
aos(config)#no shutdown
aos(config)#exit
aos(config)#no shutdown
aos(config)#exit
3. Create VLANs and make interfaces 1 and 2 as member ports of this VLANs.
aos(config)#vlan 1
aos(config-vlan)# ports gigabitethernet 0/1-2
aos(config)#exit
aos(config)#vlan 2
aos(config)#exit
Change the global Default MD level as 7 and MIP creation criteria as default.
aos(config)#ethernet cfm default-domain global
To verify whether four MIPs are created,
Display details of all the configured MIPs.
aos# show ethernet cfm maintenance-point local
--------------------------------------------------
--
18 AVIAT NETWORKS
MPID DomainName Level VLAN Type Port CC-

Status
ServiceName ISID Dir MAC MP-
Status
--------------------------------------------------
----
- - 7 1 MIP Gi0/1 -
- - - 00:01:02:03:04:01
Active
- - 7 2 MIP Gi0/1
-
- - - 00:01:02:03:04:01
Active
- - 7 1 MIP Gi0/2
-
- - - 00:01:02:03:04:02
Active
- - 7 2 MIP Gi0/2 -
- - - 00:01:02:03:04:02
Active
F or starti ng MI P functi onal i ty, Port (on whi ch the MI P i s
confi gured) and VLAN (VLAN wi th whi ch MI P i s associ ated)
must exi st and must be UP and ECF M must be enabl ed on
that Port.
Associating a Set of VLANs to a Primary VLAN

This section describes the association of the VLANs to a Primary VLAN. The scope of VLAN
association is limited to ECFM entities only.
CLI Configurations
To associate a set of VLANs to a Primary VLAN
1. Enter into the global configuration mode.
2. Associate a list of VLAN IDs to a Primary VLAN.
aos(config)# ethernet cfm associate vlan-id
1,2,3 primary-vlan-id 7.
3. To disassociate VLANs from a Primary VLAN
Enter into the global configuration mode and delete the mapping of a list of VLAN IDs with a
primary VLAN.
aos(config)# no ethernet cfm associate vlan-id
2,3 primary-vlan-id 7.
260-668256-001 JULY 2015 19

One VLAN cannot be associ ated wi th more than one

Pri mary VLAN onl y.
VLAN and Pri mary VLAN cannot be the same.
Enabling Ethernet CFM

When Aviat Networks CTR 8540 switch is made up, by default ECFM is in the start state, but
operationally in disable state, that is, it does not generate, receive or reply to any of the CFM
PDUs.
For Ethernet CFM entities to function, ECFM must be enabled, and all the ECFM entities must
be configured (MD, MA, MEP and MIP).
CLI Configurations
To enable ECFM:
1. Enter into the global configuration mode
2. Enable CFM processing globally
aos(config)# ethernet cfm enable
3. Return to the privileged EXEC mode.
aos(config)# exit
To disable ECFM:
Enter into the global configuration mode and disable CFM processing globally
aos(config)# no ethernet cfm enable
Enabling ECFM on an Interface

When Aviat Networks CTR 8540 switch is made up, by default ECFM is in the start state, but
operationally in disable state, that is, it does not generate, receive or reply to any of the CFM
PDUs once ECFM gets enabled, ECFM is enabled on all the interfaces that are up.
For Ethernet CFM entities (MEP and MIP) to function, ECFM must be enabled on each inter-
face, where the CFM entities are configured, and all the ECFM entities must be configured (MD,
MA, MEP and MIP).
CLI Configurations
To enable ECFM on an interface
On enabl i ng the ECF M, i f the MEP i s confi gured as acti ve,
LoopBack (LBM) and Li nkTrace (LTM) messages can be
transmi tted and recei ved.
3. Enter into the interface configuration mode
20 AVIAT NETWORKS
4. Enable CFM processing on an interface

aos(config-if)# ethernet cfm enable
To disable ECFM on an interface:
1. Enter into the interface configuration mode and disable CFM processing on an
interface
aos(config-if)# no ethernet cfm enable
Enabling Ethernet Y.1731

By default, Y.1731 compliant features are in disabled state, that is, it does not generate, receive
or reply to any of the Y.1731 compliant CFM PDU(s).
ECFM must be enabled for Y.1731 to start functioning.
Y.1731 should be enabled for Y.1731 compliant features such as AIS, LCK and so on, to start
functioning.
CLI Configurations
To globally enable Y.1731:
3. Enable Y.1731 processing globally
aos(config)# ethernet cfm y1731 enable
4. Return to the privileged EXEC mode.
aos(config)# exit
To globally disable Y.1731:
Enter into the global configuration mode and disable Y.1731 processing globally.
aos(config)# no ethernet cfm y1731 enable
Enabling Y.1731 on an Interface

By default, Y.1731 compliant features are in disabled state, that is, it does not generate, receive
or reply to any of the CFM PDU(s).
ECFM must be enabled on the interface on which Y.1731 is to be enabled.
CLI Configurations
To enable Y.1731 on an interface:
2. Enter into the interface configuration mode.
3. Enable ECFM processing on the interface.
aos(config-if)# ethernet cfm enable
260-668256-001 JULY 2015 21

4. Enable Y.1731 processing on the interface.

aos(config-if)# ethernet cfm y1731 enable
To disable Y.1731 on an interface:
1. Enter into the interface configuration mode and disable Y.1731 processing on the
interface.
aos(config-if)# no ethernet cfm y1731 enable
On Enabl i ng the Y.1731, i f the MEP i s confi gured as acti ve,
LoopBack (LBM/LBR), Li nkTrace (LTM/LTR), Test (TST),
Al arm I ndi cati on Si gnal (AI S), Lock (LCK), One-Way Del ay
Measurement (1DM), Two-Way Del ay Measurement
(DMM/DMR), Si ngl e-ended Loss Measurement (LMM/LMR),
Dual -ended Loss Measurement messages can al so be trans-
mi tted and recei ved.
Enabling and Disabling Ethernet CCM Offload

By default, CCM offloading is enabled. If CCM off loading is disabled, 300Hz and 10ms CCMs
are not supported.
CLI Configurations
To enable CCM offloading:
Enable CCM offloading on all the MEPs
aos(config)# ethernet cfm offload
To disable CCM offloading:
Enter into the global configuration mode and disable CCM offloading on all the MEPs
aos(config)# no ethernet cfm offload
CCM Offloading can be enabled on MEP also using
set ethernet cfm offload command
Configuring and Enabling Continuity Check Messages

After configuring and enabling Continuity Check Messages, every MEP (if MD, MA and MEP are
configured) transmits CC messages as per the CCM transmission interval that is set.
CLI Configurations
To configure and enable CCM:
1. Execute the steps given in the related CLI Configurations for configuring MEP
before configuring and enabling the CC transmission parameters.
2. Enter into the global configuration mode and set the CC parameters like interval,
VLAN, and domain level.
22 AVIAT NETWORKS
aos(config)# ethernet cfm cc level 1 vlan 101

interval ten-ms
3. Enable the CC functionality.
aos(config)# ethernet cfm cc enable level 1
vlan 101
4. Return to the Privileged EXEC Mode.
aos(config)# exit
Set and enabl e CC parameters for more than one domai n
l evel s and VLANs.
5. Example: ethernet cfm cc level 1-3 vlan 101-105 interval ten-ms
6. or
7. ethernet cfm cc level 1,2,3 vlan 101,102,103,104,105 interval ten-ms
8. To reset CC transmission interval enter into the global configuration mode and
reset the CC transmission interval to default interval (1second).
aos(config)# no ethernet cfm cc level 1 vlan
101.
9. To disable CC transmission enter into the global configuration mode and disable
CC transmission on specified level and VLAN.
aos(config)# no ethernet cfm cc enable level 1
vlan 101
F or VLAN-UnAware MEPs, vl an keyword must not be
provi ded wi th the command.
ECF M shoul d be enabl ed for the successful CCMs trans-
mi ssi on.
By defaul t, CCM messages are mul ti cast and thei r rol e i s
F aul t Management.
MEP, at speci fi ed l evel and VLAN, must be enabl ed for suc-
cessful CCM transmi ssi on.
When Y.1731 i s enabl ed, user has to expl i ci tl y enabl e CCM
transmi ssi on i n an ME.
Enabling Crosscheck between Configured Remote

MEPs
This section describes enabling crosschecking between the list of configured remote MEP of a
domain and the MEPs learned through the CCMs. By default crosschecking is enabled.
CLI Configurations
To configure and enable crosschecking:
1. Execute the steps given in the related CLI Configurations for configuring MA
before enabling the crosschecking.
260-668256-001 JULY 2015 23

2. Enter into the global configuration mode and set the crosscheck parameter (start-
delay)
aos(config)# ethernet cfm mep crosscheck start-
delay 3
3. Enable the crosschecking functionality.
aos# ethernet cfm mep crosscheck enable level
1,2 vlan 101
To reset the crosscheck start delay
4. Enter into the global configuration mode and reset the crosscheck start-delay to
default delay 3.
aos(config)# no ethernet cfm mep crosscheck
start-delay.
To disable crosschecking:
5. Enter into the global configuration mode and disable crosschecking at a specified
level and VLAN.
aos(config)# ethernet cfm mep crosscheck disable
level 1,2 vlan 101.
For VLAN-UnAware MEPs, the VLAN keyword must not be provided with the command.
Configuring and Enabling LoopBack Messages

After configuring and enabling LoopBack messages, every MEP (if MD, MA and MEP are con-
figured) can transmit LoopBack messages.
CLI Configurations
To configure loopback messages:
1. Execute the steps given in the related CLI Configurations for configuring MEP
respectively before sending the LBMs.
For ECFM compliant loopback feature:
2. Execute the steps given in the related CLI Configurations to enable ECFM.
3. Send the loopback messages to the MEP destination.
aos# ping ethernet mac 00:02:02:03:04:03 level
7 vlan 101 count 1
Sending 1 Ethernet CFM loopback messages, timeout
is 5 seconds
Success rate is 100.0 percent 1/1
aos#
For Y.1731 compliant loopback feature:
4. Execute the steps mentioned in the related CLI Configurations to enable Y.1731.
5. Send the loopback messages to the MEP destination.
aos# ping ethernet mac 00:02:02:03:04:03 level 7
vlan 101 count 5
PING 00:02:02:03:04:03 from 00:01:02:03:04:03 with
0(27) bytes of data.
24 AVIAT NETWORKS
64 bytes from 00:02:02:03:04:03: seq_no=0 time=80

ms
ms
ms
ms
ms
--- 00:02:02:03:04:03 ping statistics ---
packets sent = 5, packets received = 5, packets
lost = 0 (0.000% loss),
unexpected received = 0, duplicate received = 0,
bad received = 0,
checksum errors = 0, responders = 1, average
packets per responder = 5,
rtt min/avg/max = 80/80/80 ms
aos#
The above menti oned steps are onl y for i ni ti ati ng the l oop-
back message. User may not get the same output. To get
the same output, target enti ty al so needs to be con-
fi gured.
For sending Loopback messages to a MEP destination using MEPID:
Example: ping ethernet mpid 101 level 7 vlan 101 count 3
The MACAddress of the MEP with specified target “mpid” must be learned prior to the exe-
cution of the command.
For a VLAN-UnAware MEP, vlan keyword must not be provided with the command.
In ECFM, “count”, if not provided, number of loopback messages to send is considered as one.
In case Y.1731 is enabled, “count” and “deadline” keyword, if not provided, assumes infinite
number of loopback messages to send.
6. If user does not provide target MPID and MAC Address, it will be treated as mul-
ticast loopback messages.
MEP at specified level and VLAN must be enabled for a loopback transaction. The loopback
(ping) capability can be enabled using either set params capability enable ping (runs in ECFM
MEP configuration mode) or ethernet cfm mep-capability enable level vlan ping (runs in Global
Configuration mode)command.
Example:
aos(config-ether-mep)# set params capability
enable ping
aos(config)# ethernet cfm mep-capability enable
level 7 vlan 101 ping
260-668256-001 JULY 2015 25

Configuring and Enabling Linktrace Messages

After configuring and enabling LTMs, every MEP (if MD, MA and MEP are configured) can
transmit LTMs.
CLI Configurations
To configure linktrace message
1. Execute the steps given in the related section CLI Configurations to configure MEP
before sending the LTMs.
For ECFM compliant linktrace feature:
2. Execute the steps given in the related CLI Configurations to enable ECFM.
3. Enable linktrace caching on the device.
aos# config terminal
aos(config)# ethernet cfm traceroute cache
aos(config)# end
4. Send the LTM to an MEP destination.
aos# traceroute ethernet mac 00:02:02:03:04:02
level 7 vlan 101 time-to-live 32
Traceroute to Macaddress 00:02:02:03:04:02 in
domain TestDomain1 at level 7
with vlanId 101
--------------------------------------------------
--
Hops Host Ingress MAC
Ingress Action Relay Action
Next Host Egress MAC
Egress Action Fwd Status
--------------------------------------------------
--
1 00:01:02:03:04:01:00:02 00:02:02:03:04:02
IngOK RlyHit
00:02:02:03:04:01:00:02 - -
Terminal MEP
aos#
For Y.1731 compliant linktrace feature:
5. Execute the steps in the related CLI Configurations to enable Y.1731.
6. Enable linktrace caching on the device.
aos# config terminal
aos(config)# ethernet cfm traceroute cache
aos(config)# end
7. Send the LTMs to the MEP destination.
level 7 vlan 101
26 AVIAT NETWORKS

domain meg1 at level 7
with vlanId 101
--------------------------------------------------
----
Hops Host Ingress MAC
Ingress Action Relay Action
Next Host Egress MAC
Egress Action Fwd Status
--------------------------------------------------
----
1 00:00:00:00:00:00:00:00 - -
RlyHit
00:00:00:00:00:00:00:00 00:01:02:03:04:02
EgrOK Not Forwarded
The above menti oned steps are onl y for i ni ti ati ng the l i nk-
trace message. User may not get the same output. To get
the same output, target enti ty al so needs to be con-
fi gured.
For sending a Linktrace message to an MEP destination using MEPID
Example: traceroute ethernet mpid 101 level 7 vlan 101 time-to-live 32
Mac Address of MEP with specified target mpid must be learned prior to the execution of the
command.
For a VLAN-UnAware MEP, vlan keyword must not be provided with the command.
MEP at specified level and VLAN must be enabled for a traceroute transaction.
ECFM should be enabled for the successful traceroute message transmission
In case Y.1731 is enabled, user can also provide the time within which LTR should be received.
Example: traceroute ethernet mpid 101 level 7
vlan 101 timeout 10
This implies that the responder will wait only for 10 seconds for the trace-route reply.
Configuring and Enabling Alarm Indication Signal

Messages
This section describes the steps to configure and enable the transmission of AIS PDU by an
MEP.
CLI Configurations
To configure and enable AIS messages:
1. Execute the steps given in the related CLI Configurations to configure MEP before
sending the AIS messages.
2. Execute the steps given in the related CLI Configurations to enable ECFM and
Y.1731.
260-668256-001 JULY 2015 27

3. Configure client layer level.

TestDomain1 level 7
CTR 8540 (config-ether-ecfm)# client-layer-level
6
aos# end
4. Enable AIS capability on the MEP, so that when any defect occurs, the MEP starts
transmitting the AIS to all the MEP(s) configured at the client layer level.
aos(config-if)# ethernet cfm mep level 3 inward
mpid 4 vlan 5 active
aos(config-ether-mep)# set ais enable
aos(config-ether-mep)# end
AI S capabi l i ty can al so be enabl ed usi ng ethernet cfm
mep-capabi l i ty enabl e l evel 3 vl an 5 ai s command
Cl i ent l ayer l evel must be confi gured before enabl i ng AI S
capabi l i ty.
AI S can be send as uni cast messages by confi guri ng i ts
uni cast MAC address usi ng set cl i ent-l ayer-mac ai s uni -
cast command. (Thi s command runs i n ECF M Mep con-
fi gurati on Mode.)
Exampl e: set cl i ent-l ayer-mac ai s uni cast
00:01:02:03:04:06
5. OR
6. Starting the Two-way Throughput Measurement at an MEP using destination
MAC address.
aos# ethernet cfm throughput type two-way mac
00:01:02:03:04:04 level 7 vlan 101
count 15
600, packet size 1522 bytes- 00:01:02:03:04:04
two-way throughput statistics -final throughput
1200000 / 1.200000, packet size 1500
bytestransmission rate = 100 pps 1217600/1.2
Setting OUI (Organizational Unit Identifier)

This section describes the steps required to configure the OUI globally on a device.
CLI Configurations
To configure the OUI globally on a device
28 AVIAT NETWORKS
2. Set the OUI

aos(config)# set ethernet-cfm oui 02:03:04.
Defaul t val ue corresponds to the fi rst three bytes of the
System MAC Address.
3. Return to the Privileged Exec Mode.
aos(config)# exit
To set the OUI to default value:
4. Enter into the global configuration mode and reset the OUI to default value.
aos(config)# no set ethernet-cfm oui.
Enabling LLC Encapsulation on interface

This section describes the steps to enable the CFM PDU encapsulation in LLC header on the spe-
cified port.
CLI Configurations
To enable LLC encapsulation on a port
2. Enter into the interface configuration mode.
3. Enable the LLC encapsulation on the port.
aos(config-if)# ethernet cfm llc-encap enable
4. Return to the global configuration mode.
To disable LLC encapsulation:
5. Enter into the interface configuration mode and disable the ECFM.
aos(config-if)# ethernet cfm llc-encap disable
Displaying Ethernet CFM Entities

This section describes the viewing of information related to configured ECFM and Y.1731 entit-
ies in SI mode.
CLI Configurations
ECFM entities are displayed on the Aviat Networks CTR 8540 shell. Aviat Networks ECFM
provides the following show commands for displaying the ECFM entities:
show ethernet cfm domain [brief]
show ethernet cfm service [brief]
show ethernet cfm maintenance-point local [ mep
| mip ] [ interface interface-type interface-
number | domain domain-name | level level- id ]
260-668256-001 JULY 2015 29

Displaying Maintenance Domain

This section describes the command that is used to display the information (displays the main-
tenance domain name, index, level, associated number of services configured and MEP archive
time for all the Maintenance Domain configured on the bridge) of the CFM Maintenance
Domains configured in the system.
CLI Configurations
Display the MD configured on the bridge.
aos# show ethernet cfm domain brief
Domain Name Index Level Services Archive
(min)
oper1 1 4 1 100
oper2 2 3 1 100
oper3 3 5 0 100
Displaying Maintenance Association

This section describes the command that is used to display the details (displays the main-
tenance association name, domain name, level, primary VLAN, level, associated number of
maintenance end points which are statically defined and CCM Interval for all the Maintenance
Association configured on the bridge) of all the CFM Maintenance Associations (Services) con-
figured in the system.
CLI Configurations
Display the MA configured on the bridge.
aos# show ethernet cfm service brief
ServiceName Index Primary-Vlan ISID Level MEPs
CCM Interval
maoper1 1 3 - 4 0 1
second
maoper2 1 4 - 3 2 10
milliseconds
maoper3 2 1 - 2 0 10
minutes
Displaying Maintenance Points configured

This section describes the command that is used to display the maintenance points configured
in the system.
CLI Configurations
Display the MEPs configured on the bridge.
30 AVIAT NETWORKS

mep
--------------------------------------------------
----
Status
Status
--------------------------------------------------
----
1 Oper1 0 - MEP Gi0/3 Disabled
maOper1 - Down
00:01:02:03:04:03 Active
2 Oper2 1 - MEP Gi0/3 Disabled
maOper2 Down
0:01:02:03:04:03 Active
1 Oper3 2 1 MEP Gi0/3
Disabled
maOper3 - Down
00:01:02:03:04:03 Active
260-668256-001 JULY 2015 31

Chapter 3. Flow Based

Configuration
Creating Interfaces
This section describes the creation and configuration of interfaces at CUST1, CUST2 and CUST3.
CLI Configurations
At CUST1, CUST2 and CUST3
Enable interfaces
aos(config-if)# no shutdown
Creating VLAN
This section describes the creation of VLAN on bridges (CUST1, CUST2 and CUST3) and assign-
ing of member ports for the created VLAN.
CLI Configurations
Create VLAN and assign member ports for this VLAN
aos(config)# vlan 2
aos(config-vlan)# vlan active
aos(config-vlan)# exit
260-668256-001 JULY 2015 33

CHAPTER 3. FLOW BASED CONFIGURATION
Enabling ECFM, Traceroute Caching and MIP CCM

Database
This section describes the enabling of ECFM, traceroute caching and MIP CCM database on
bridges (CUST1, CUST2, CUST3).
CLI Configurations
Enable ECFM
aos(config) # ethernet cfm enable
Enable Traceroute caching
aos(config) # ethernet cfm traceroute cache
Enable MIP CCM database
aos(config) # ethernet cfm mip ccm-database
Configuring Maintenance Domain, Service and MEPs

This section describes the configuration of MD, MA and MEPs on bridges.
CLI Configurations
At CUST1 and CUST3
Configure MD, Service and MEP list
aos(config) # ethernet cfm domain name OP1 level
5
aos(config-ether-ecfm) # service name maop1
vlan 2
aos(config-ether-ecfm)# mep crosscheck mpid 10
vlan 2
aos(config-ether-ecfm)# mep crosscheck mpid 30
vlan 2
aos(config-ether-ecfm)# end
At CUST1
Configure the Down MEP.
vlan 2 active
At CUST3
Configure the Down MEP.
34 AVIAT NETWORKS

vlan 2 active
Enabling CCM transmission

This section describes the enabling of the CCM transmission on bridges CUST1 and CUST3
CLI Configurations
At CUST1 and CUST3
Enable CCM transmission
aos(config)# ethernet cfm cc enable level 5 vlan
2
aos(config)# exit
Configuring MIP
This section describes the configuration of Default Domain with VLAN and MdLevel for MIP cre-
ation, and configuration of MIP in the default domain on the bridge CUST2.
CLI Configurations
At CUST2
Configure default domain and MIP
aos(config) # ethernet cfm default-domain vlan 2
aos(config-if)# ethernet cfm mip level 5 vlan 2
active
Verifying Configured MPs (MEP and MIP)

This section describes the verification of the configured MEP and MIP on the bridges.
CLI Configurations
At CUST1
Display the details of all the MEPs and MIPs.
--------------------------------------------------
----
Status
260-668256-001 JULY 2015 35


Status
--------------------------------------------------
----
10 OP1 5 2 MEP Gi0/2
Enabled
maop1 - Down
00:01:02:03:04:02 Active
At CUST2
--------------------------------------------------
----
Status
Status
--------------------------------------------------
----
- - 5 2 MIP Gi0/2
-
- - - 00:02:02:03:04:02
Active
At CUST3
--------------------------------------------------
----
Status
Status
--------------------------------------------------
----
30 OP1 5 2 MEP Gi0/2 Enabled
maop1 - Down 00:03:02:03:04:02
Active
Checking for CCM Errors

This section describes the checking of CCM errors on the bridges (CUST1 and CUST3)
36 AVIAT NETWORKS
CLI Configurations
At CUST1
Display the logged CFM continuity check error conditions
aos# show ethernet cfm errors
MEP-ID : 10
Level VLAN RMEP-ID Current defect type
----- ---- ------- -------------------
5 2 30 mac status defect
1. Implies that CUST-3 is sending CCM with port-status as blocked.
At CUST3
MEP-ID : 30
----- ---- ------- -------------------
5 2 10 remote defect indication
2. Implies that CUST-1 is sending CCM with RDI as enabled.
Checking for Configured Remote Entities in the

Network
This section describes the checking of configured MAs.
CLI Configurations
At CUST1
Display information about all the configured CFM MAs
aos# show ethernet cfm service
Service Name : maop1
Domain Name : OP1
Index : 1
Primary Vid : 2
Level : 5
MHF Creation Criteria : defer
Sender Id Permission : defer
CC Role : fault management
ICC Code : maop1
UMC Code : OP1
Total MEPs : 2
Primary Vlan Associations :
None
260-668256-001 JULY 2015 37

Crosscheck status : Enabled

Crosscheck:
MPID VLAN ISID Type Mep-Up Mac Address
10 2 - Local Yes
0:01:02:03:04:02
30 2 - Remote Yes
00:03:02:03:04:02
At CUST3
Display information about all the configured CFM MAs
aos# show ethernet cfm service
Service Name : maop1
Domain Name : OP1
Index : 1
Primary Vid : 2
Level : 5
MHF Creation Criteria : defer
Sender Id Permission : defer
CC Role : fault management
ICC Code : maop1
UMC Code : OP1
Total MEPs : 2
Primary Vlan Associations :
None
Crosscheck status : Enabled
Crosscheck:
MPID VLAN ISID Type Mep-Up Mac
Address
10 2 - Remote Yes
00:01:02:03:04:02
30 2 - Local Yes
00:03:02:03:04:02
Generating CCM Errors

This section describes the generation of CCM errors. Interface P2 of CUST3 is made down, to
raise a defect/fault in sample topology.
CLI Configurations
At CUST3
Make interface P2 down.
aos(config-if)# shutdown
38 AVIAT NETWORKS
Wait for 5 seconds and verify any link failure (error/fault/defect)

At CUST1
MEP-ID : 10
----- ---- ------- -------------------
5 2 30 ccm life time expired
At CUST2
3. Shows no error,as MIP cannot detect any link failure (error/fault/defect).
At CUST3
MEP-ID : 30
----- ---- ------- -------------------
5 2 10 ccm life time expired
Verifying and Isolating Fault

This section describes the verification and isolation of fault using loopback and link trace mes-
sages.
CLI Configurations
At CUST1
Initiate the Loopback transaction from CUST1 to MEP at CUST3 to verify the link failure, where
CUST3 MEP’s MAC Address is the learned remote MAC Address known from the command
show ethernet cfm service
aos# ping ethernet mac 00:03:02:03:04:02 domain
OP1 vlan 2
is 5 seconds
aos#
Initiate Traceroute to MEP at bridge CUST3 to isolate link failure (error/fault/defect).
domain OP1 vlan 2
domain OP1 at level 5
with vlanId 2
260-668256-001 JULY 2015 39

--------------------------------------------------
----
Hops Host Ingress MAC Ingress Action Relay
Action
Next Host Egress MAC Egress Action Fwd
Status
--------------------------------------------------
----
1 00:01:02:03:04:01:00:02 00:02:02:03:04:02
IngOK RlyFDB
00:02:02:03:04:01:00:02 00:02:02:03:04:03
EgrOK Forwarded
Shows there is a link failure between CUST1 and CUST3, as no reply is received from CUST3 and
with the Relay Action as RlyHit
Initiate the Loopback transaction to MIP at CUST2 to verify if there is a link failure.
OP1 vlan 2
is 5 seconds
4. Shows no link failure between CUST1 and CUST2
Bridge Up Interface
This section describes the configuration of interface.
CLI Configurations
At CUST3
Make interface P2 of CUST3 as up.
Wait for 5 seconds and check error/fault/defect.
Checking for CCM Errors

This section describes the checking of CCM errors after configuring the interface as up.
CLI Configurations
At CUST1
Wait for 5 seconds after configuring the interface as up and then check for error/fault/defect
MEP-ID : 10
40 AVIAT NETWORKS
----- ---- ------- -------------------

5 2 30 mac status defect
5. Implies that CUST-3 is sending CCM with port-status as blocked.
At CUST3
Wait for 5 seconds after configuring the interface as up and then check for error/fault/defect
MEP-ID : 30
----- ---- ------- -------------------
5 2 10 remote defect indication
6. Implies that CUST-1 is sending CCM with RDI as enabled.
Verifying and Isolating Fault

This section describes the initiation of the loop back and link trace messages to verify and isol-
ate fault.
CLI Configurations
At CUST1
Initiate the Loopback transaction from MEP at CUST1 to MEP at CUST3.
OP1 vlan 2
is 5 seconds
Initiate Traceroute from MEP at CUST1 to MEP at CUST3
domain OP1 vlan 2
domain OP1 at level 5
with vlanId 2
--------------------------------------------------
----
Hops Host Ingress MAC Ingress Action Relay
Action
Next Host Egress MAC Egress Action Fwd
Status
--------------------------------------------------
----
1 00:01:02:03:04:01:00:02 00:02:02:03:04:02
IngOK RlyFDB
00:02:02:03:04:01:00:02 00:02:02:03:04:03
EgrOK Forwarded
260-668256-001 JULY 2015 41

2 00:02:02:03:04:01:00:02 00:03:02:03:04:02
IngBlocked RlyHit
00:03:02:03:04:01:00:02 -
- Terminal MEP
Enabling Y1731
This section describes the enabling of Y.1731.
CLI Configurations
Enable Y.1731
aos(config) # ethernet cfm y1731 enable
aos(config) # exit
Initiating Frame Delay Measurement

This section describes the intiation of frame delay measurement.
CLI Configurations
At CUST1
Initiate Two-way Frame delay measurement from MEP at CUST1 to MEP at CUST3.
aos# ethernet cfm frame delay start type two-way
level 5 vlan 2 mac 00:03:02:03:04:02 count 5
Wait for 5 seconds and view the frame delay buffer to see the result.
aos# show ethernet cfm frame delay buffer detail
Interface : gigabitethernet 0/2
MEP-ID : 10
Level : 5
VLAN-ID : 2
peer mac-address frame-delay IFDV FDV
----------------- ----------- ---- ---
00:03:02:03:04:02 110.0ms 0.000ms
0.000ms
00:03:02:03:04:02 120.0ms 10.00ms
10.00ms
00:03:02:03:04:02 120.0ms 10.00ms
0.000ms
00:03:02:03:04:02 120.0ms 10.00ms
0.000ms
00:03:02:03:04:02 120.0ms 10.00ms
0.000ms
42 AVIAT NETWORKS
- 00:01:02:03:04:02 two-way frame delay statistics

---
timestamp = 12 Aug 2008 9:52:22, packets sent = 5,
packets received = 5,
delay min/avg/max = 110.0ms/118.0ms/120.0ms,
variation avg IFDV/FDV = 8.000ms/2.000ms
Initiating Frame Loss Measurement

This section describes the intiation of frame loss measurement.
CLI Configurations
At CUST1
Initiate Frame loss measurement from MEP at CUST1 to MEP at CUST3.
aos# ethernet cfm frame loss level 5 vlan 2 mac
00:03:02:03:04:02 count 5
Wait for 5 seconds and view the frame loss buffer to see the result.
aos# show ethernet cfm frame loss buffer detail
Interface : gigabitethernet 0/2
MEP-ID : 10
Level : 5
VLAN-ID : 2
peer mac-address near-end loss far-end loss
measurement time taken
----------------- ------------- ------------
----
00:03:02:03:04:02 0 0
100ms
00:03:02:03:04:02 1 1
100ms
00:03:02:03:04:02 1 1
100ms
00:03:02:03:04:02 1 1
100ms
00:03:02:03:04:02 1 1
100ms
- 00:01:02:03:04:02 single-ended frame loss
statistics
timestamp = 12 Aug 2008 9:59:10, packets sent = 5,
packets received = 5,
near-end loss max/avg/min = 1/0/0,
far-end loss max/avg/min = 1/0/0
260-668256-001 JULY 2015 43

Initiating Test Message

This section describes the intiation of the test messages.
CLI Configurations
At CUST1
Initiate Test message from MEP at CUST1 to MEP at CUST3.
aos# ethernet cfm test mac 00:03:02:03:04:02
domain OP1 vlan 2 count 5
TST to 00:03:02:03:04:02 from 00:01:02:03:04:02
with 33(64) bytes of data.
60 bytes to 00:03:02:03:04:02: seq_no=0
60 bytes to 00:03:02:03:04:02: seq_no=1
60 bytes to 00:03:02:03:04:02: seq_no=2
60 bytes to 00:03:02:03:04:02: seq_no=3
60 bytes to 00:03:02:03:04:02: seq_no=4
--- 00:03:02:03:04:02 test statistics ---
packets sent = 5 with prbs signal without crc32
pattern
Initiating Availability Measurement

This section describes the initiation of Availability Measurement.
CLI Configurations
At CUST1
Initiate Availability measurement from MEP at CUST1 to MEP at CUST3.
aos# ethernet cfm availability measurement level
5 vlan 2 mac 00:03:02:03:04:02 window 5 interval
1000 deadline 60
Wait for 60 seconds to see the Availability Percentage
aos# show ethernet cfm availability percentage
Switch default
Interface : Gi0/1
MEP-ID : 2
Level : 4
VLAN-ID : 10
ISID : -
Availability Percentage : 100.0
44 AVIAT NETWORKS
260-668256-001
WWW.AVIATNETWORKS.COM

CTR 8500-8300 3.0 ECFM Config July2015 260-668256-001

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

CTR 8500-8300 3.0 ECFM Config July2015 260-668256-001

Загружено:

Авторское право:

Доступные форматы

CTR 8300/8500 CONFIGURATION

260-668256-001 JULY 2015 I

Aviat Networks Technical & Sales

Sales and Sales Support

Product Compliance Notes

International Use of 5.8GHz

260-668256-001 JULY 2015 III

Declaration of Conformity, R&TTE Directive, 1999/5/EC

260-668256-001 JULY 2015 V

ECFM Configuration Table of Contents

CHAPTER 1. INTRODUCTION TO ECFM 1

CHAPTER 2. CONFIGURING ECFM 11

260-668256-001 JULY 2015 VII

Configuring Maintenance End Points 14

CHAPTER 3. FLOW BASED CONFIGURATION 33

VIII AVIAT NETWORKS

Initiating Frame Loss Measurement 43

260-668256-001 JULY 2015 IX

Chapter 1. Introduction to ECFM

Purpose and Scope

260-668256-001 JULY 2015 1

IPDV Inter-Packet Delay Variation

IEEE 802.1ag and ITU-T Y.1731 Terminology Mapping

Red code Output of the configured value

260-668256-001 JULY 2015 3

Command Mode Access Method Prompt Exit method

ECFM Protocol Description

260-668256-001 JULY 2015 5

Figure 2-1. Maintenance Domain in ECFM

Maintenance Association / Service Instance

Figure 2-2. Maintenance Association

Figure 2-3. Example Maintenance Association

260-668256-001 JULY 2015 7

MHF (MIP Half Function) Functions

Continuity Check Protocol

Alarm Indication Signal

260-668256-001 JULY 2015 9

Chapter 2. Configuring ECFM

260-668256-001 JULY 2015 11

Configuring the ECFM Capabilities

Configuring Maintenance Domain

To delete configured MD:

Configuring Maintenance Association

aos(config-ether-ecfm)# service name CustAssoc1

260-668256-001 JULY 2015 13

aos(config-ether-ecfm)# no service format

Configuring Maintenance End Points

Configuring Maintenance Intermediate Points

MIP associated with an MA

260-668256-001 JULY 2015 15

1. MA must be configured at same MD level and VLAN at which MIP is to be con-

MIP associated with Default Domain

aos(config)# ethernet cfm default-domain vlan

Implicit MIP Creation

MIP creation evaluation process

260-668256-001 JULY 2015 17

2. The MD level of each of the MA that includes VLAN x.

MPID DomainName Level VLAN Type Port CC-

Associating a Set of VLANs to a Primary VLAN

260-668256-001 JULY 2015 19

One VLAN cannot be associ ated wi th more than one

Enabling Ethernet CFM

Enabling ECFM on an Interface