ECFMConfigUM PDF

ECFM aricent.
com
Configuration User Manual
ARICENT: ECFMConfigum/20090603
Revision Number: 11.0

Copyright © 2009 Aricent Inc. All Rights Reserved. No part of this document may be reproduced,
stored in a retrieval system or transmitted, in any form, or by any means, electronic or otherwise,
including photocopying, reprinting, or recording, for any purpose, without the express written permission
of Aricent.
Printed in ________
TRADEMARKS ARICENT and THE ARICENT LOGO are trademarks of Aricent Inc. in the U.S. and
other countries. The use of any of these trademarks without Aricent prior written consent is strictly
prohibited. Other trademarks and trade names may be used in this document to refer to either the
entities claiming the marks and names or their products. Aricent Inc. disclaims any proprietary interest in
the trademarks and trade names other than its own.
DISCLAIMER The information in this book is provided “as is”, with no warranties whatsoever, including
any warranty of merchantability, fitness for any particular purpose or any warranty otherwise arising out
of any proposal, specification or sample. This document is provided for informational purposes only and
should not be construed as a commitment on the part of Aricent. Information in this document is subject
to change without notice.
REQUESTS For information or obtaining permission for use of material of this work, please submit a
written request to: Corporate Marketing and Legal, 700 Hansen Way, Palo Alto, CA 94304.
DOCUMENT No.: ARICENT: ECFMConfigum/20090603
Contents
CHAPTER 1: 1. INTRODUCTION _____________________________________________ 13

1.1 PURPOSE AND SCOPE ................................................................................ 13
1.2 ACRONYMS AND ABBREVIATIONS ................................................................ 13
1.3 IEEE 802.1AG AND ITU-T Y.1731 TERMINOLOGY MAPPING ........................ 15
1.4 REFERENCES ............................................................................................. 15
1.5 DOCUMENT CONVENTIONS ......................................................................... 16
1.6 GENERAL CONFIGURATIONS ....................................................................... 16
1.6.1 CLI Configurations ................................................................................ 16
1.6.2 SNMP Configurations............................................................................ 17
1.6.2.1 SNMP Operations----------------------------------------------------------------- 17
1.6.2.1.1 MIB Load------------------------------------------------------------------------ 17
1.6.2.1.2 Set Operation ------------------------------------------------------------------ 19
1.6.2.1.3 Get Operation------------------------------------------------------------------ 19
1.6.2.1.4 Walk Operation ---------------------------------------------------------------- 20
1.6.2.2 Interface Range ------------------------------------------------------------------- 20
CHAPTER 2: 2. PRODUCT DESCRIPTION _____________________________________ 23
2.1 ETHERNET CFM ........................................................................................ 23
2.2 MAINTENANCE DOMAIN .............................................................................. 24
2.3 MAINTENANCE ASSOCIATION / SERVICE INSTANCE ....................................... 25
2.4 MAINTENANCE POINT ................................................................................. 26
2.5 MEP FUNCTIONS ....................................................................................... 26
2.6 MHF (MIP HALF FUNCTION) FUNCTIONS .................................................... 27
2.7 CFM FEATURES ........................................................................................ 27
2.7.1 Fault Management ................................................................................ 27
2.7.1.1 Continuity Check Protocol ------------------------------------------------------ 27
2.7.1.2 LoopBack Protocol---------------------------------------------------------------- 27
2.7.1.3 LinkTrace Protocol ---------------------------------------------------------------- 28
2.7.1.4 Alarm Indication Signal ---------------------------------------------------------- 28
2.7.1.5 Locked Signal (LCK) ------------------------------------------------------------- 28
2.7.1.6 Test Signal (TST) ----------------------------------------------------------------- 28
2.7.1.7 Maintenance Communication Channel (MCC)----------------------------- 29
2.7.1.8 Experimental OAM (EXP) ------------------------------------------------------- 29
2.7.1.9 Vendor Specific OAM (VSP) --------------------------------------------------- 29
2.7.2 Performance Monitoring........................................................................ 29
2.7.2.1 Frame Loss Measurement ------------------------------------------------------ 29
2.7.2.2 Frame Delay Measurement----------------------------------------------------- 30
2.7.2.3 Frame Delay Variation Measurement ---------------------------------------- 30
2.7.2.4 Through Measurement----------------------------------------------------------- 30
CHAPTER 3: 3. CONFIGURING ECFM IN SINGLE INSTANCE MODE _______________ 31
3.1 CONFIGURATION GUIDELINES ..................................................................... 31
3.2 DEFAULT CONFIGURATIONS ........................................................................ 32
3.3 CONFIGURING THE ECFM CAPABILITIES ..................................................... 32
3.3.1 Configuring Maintenance Domain......................................................... 32
3.3.1.1 CLI Configurations ---------------------------------------------------------------- 32
3.3.1.2 SNMP Configurations ------------------------------------------------------------ 33
3.3.2 Configuring Maintenance Association................................................... 34
3.3.3 Configuring Maintenance End Points.................................................... 35
CONFIGURATION USER MANUAL 1

ARICENT CONFIDENTIAL
ECFM

3.3.4 Configuring Maintenance Intermediate Points ...................................... 37
3.3.4.1.1 Explicit MIP Creation --------------------------------------------------------- 37
3.3.4.1.2 Implicit MIP Creation --------------------------------------------------------- 39
3.3.4.2.1 Explicit MIP Creation --------------------------------------------------------- 41
3.3.4.2.2 Implicit MIP Creation --------------------------------------------------------- 43
3.3.5 Associating a Set of VLANs to a Primary VLAN ................................... 44
3.3.6 Enabling Ethernet CFM......................................................................... 45
3.3.7 Enabling ECFM on an Interface ............................................................ 46
3.3.8 Enabling Ethernet Y.1731 ..................................................................... 47
3.3.9 Enabling Y.1731 on an Interface........................................................... 47
3.3.10 Enabling Ethernet CCM Offload............................................................ 48
3.3.11 Configuring and Enabling Continuity Check Messages ........................ 49
3.3.12 Enabling Crosscheck Between Configured Remote MEPs .................. 51
3.3.13 Configuring and Enabling LoopBack Messages ................................... 52
3.3.14 Configuring and Enabling Linktrace Messages..................................... 54
3.3.15 Configuring and Enabling Test Messages ............................................ 57
3.3.16 Configuring and Enabling Frame Delay Measurement......................... 59
3.3.17 Configuring and Enabling Frame Loss Measurement........................... 61
3.3.18 Configuring and Enabling Alarm Indication signal Messages............... 64
3.3.19 Configuring and Enabling Lock Messages............................................ 65
3.3.20 Configuring and Enabling Throughput Measurement ........................... 67
2 ARICENT: ECFMCONFIGUM/20090603
CONTENTS
3.3.21 Setting OUI (Organizational Unit Identifier)........................................... 69

3.3.22 Enabling LLC Encapsulation on interface ............................................. 70
3.4 DISPLAYING ETHERNET CFM ENTITIES ....................................................... 70
3.4.3 Displaying Maintenance Domain........................................................... 71
3.4.4 Displaying Maintenance Association .................................................... 72
3.4.5 Displaying Maintenance Points configured ........................................... 73
CHAPTER 4: 4. CONFIGURING ECFM IN MULTIPLE INSTANCE MODE _____________ 75
4.1 CREATING VIRTUAL CONTEXT ..................................................................... 76
4.2 CREATING VLAN ....................................................................................... 78
4.3 INITIALIZING ECFM .................................................................................... 79
4.4 CONFIGURING MAINTENANCE DOMAIN, SERVICE AND MEPS ........................ 79
4.5 DETECTING FAULT ..................................................................................... 81
4.6 VERIFYING AND ISOLATING FAULT ............................................................... 82
4.7 INITIALIZING Y.1731 ................................................................................... 84
4.8 MEASURING FRAME LOSS........................................................................... 85
4.9 MEASURING FRAME DELAY ......................................................................... 86
4.10 INITIATING TEST MESSAGE ......................................................................... 87
4.11 CREATING TEST MD .................................................................................. 88
CHAPTER 5: 5. FLOW BASED CONFIGURATION _______________________________ 93
5.1 CONFIGURING ECFM ON CUSTOMER BRIDGES ........................................... 93
5.1.1 Creating Interfaces................................................................................ 94

ECFM

5.1.2 Creating VLAN ...................................................................................... 95
5.1.3 Enabling ECFM, Traceroute Caching and MIP CCM Database ........... 96
5.1.4 Configuring Maintenance Domain, Service and MEPs......................... 97
5.1.5 Enabling CCM transmission.................................................................. 99
5.1.6 Configuring MIP................................................................................... 100
5.1.6.1 CLI Configurations -------------------------------------------------------------- 100
5.1.6.2 SNMP Configurations ---------------------------------------------------------- 100
5.1.7 Verifying Configured MPs (MEP and MIP).......................................... 100
5.1.8 Checking for CCM Errors .................................................................... 103
5.1.9 Checking for Configured Remote Entities in the Network................... 104
5.1.10 Generating CCM Errors ...................................................................... 106
5.1.11 Verifying and Isolating Fault................................................................ 107
5.1.12 Bridge Up Interface ............................................................................. 110
5.1.15 Enabling Y1731 ................................................................................... 115
5.1.16 Initiating Frame Delay Measurement .................................................. 115
5.1.17 Initiating Frame Loss Measurement.................................................... 116
5.1.18 Initiating Test Message ....................................................................... 118
5.2 CONFIGURING ECFM ON PROVIDER BRIDGES ........................................... 119
5.2.1 Configuring the Bridge Mode .............................................................. 120
CONTENTS

5.2.2 Configuring Interfaces on Switches .................................................... 122
5.2.3 Configuring VLAN on Switches ........................................................... 124
5.2.4 Configuring Interface Types and VLAN Mapping................................ 125
5.2.5 Initializing ECFM ................................................................................. 129
5.2.6 Configuring Maintenance Domain, Service and MEPs....................... 130
5.2.7 Verifying the configured MP (MEP, MIP)s .......................................... 146
5.2.8 Shutdown interface ............................................................................. 159
5.2.11 Bridge UP interface ............................................................................. 165
5.2.14 Initializing Y.1731 ................................................................................ 168
5.2.15 Checking AIS and LCK features ......................................................... 169
5.3 CONFIGURING ECFM ON PROVIDER BACKBONE BRIDGES.......................... 176
5.3.1 Enabling the Provider Backbone Bridging .......................................... 177
5.3.2 Configuring the Default Bridge Mode and Interfaces .......................... 177
5.3.3 Configuring Provider Bridge Mode ...................................................... 185

ECFM
5.3.5 Configuring Interface Type.................................................................. 190

5.3.6 Configuring VLAN and VLAN-mapping............................................... 194
5.3.7 Configuring ECFM and PBB ............................................................... 197
5.3.8 Detecting Fault .................................................................................... 212
5.4 CONFIGURING Y.1731 ON PROVIDER BACKBONE BRIDGES ........................ 220
5.4.1 Enabling the Provider Backbone Bridging .......................................... 221
5.4.2 Configuring Default Bridge Mode and Interfaces ................................ 221
5.4.3 Configuring Provider Bridge Mode ...................................................... 229
5.4.5 Configuring Interface Type.................................................................. 234
5.4.6 Configuring VLAN and VLAN-mapping............................................... 238
5.4.7 Configuring Y.1731 and PBB .............................................................. 241
5.4.8 Enabling Y.1731 on all Switches......................................................... 254
5.4.9 Detecting Fault .................................................................................... 255
5.4.10 Check for Continuity Defects............................................................... 256
5.4.11 Configuring and Enabling AIS ............................................................. 257
5.4.12 Configuring and Enabling LCK............................................................ 258
5.4.13 Verifying One-Way Connectivity Using TST ....................................... 259
5.4.14 Monitoring Performance...................................................................... 260
CONTENTS
5.4.14.1 Configuring Frame Delay Measurement----------------------------------- 260

5.4.14.1.1 CLI Configurations---------------------------------------------------------- 260
5.4.14.1.2 SNMP Configurations ------------------------------------------------------ 261
5.4.14.2 Configuring Frame Loss Measurement ------------------------------------ 261
5.4.14.3 Configuring Throughput Measurement ------------------------------------ 263
YOUR OPINION MATTERS _____________________________________ 265
REVISION HISTORY __________________________________________ 267

Figures
Figure 2-1 Maintenance Domain in ECFM.................................................................................................. 24

Figure 2-2 Maintenance Association........................................................................................................... 25
Figure 2-3 Example Maintenance Association............................................................................................ 25
Figure 2-4 Maintenance Point in ECFM...................................................................................................... 26
Figure 4-1: Configuration of ECFM with MI................................................................................................. 75
Figure 5-1: Configuration of ECFM on customer bridges ........................................................................... 94
Figure 5-2: Configuration of ECFM on Provider bridges........................................................................... 119
Figure 5-3: Configuration of ECFM on Provider Backbone bridges.......................................................... 176
Figure 5-4: Configuration of Y1731 on Provider Backbone bridges ......................................................... 220

Tables
Table 1-1: Acronyms Used in this Document.............................................................................................. 13

Table 1-2: Terminology Mapping ................................................................................................................ 15
Table 1-3: Conventions ............................................................................................................................... 16
Table 1-4: General Configurations.............................................................................................................. 16
Table 1-5: MIB Files .................................................................................................................................... 18
Table 1-6: Interface Index Range ............................................................................................................... 20
Table 1-7: Scalability Constants ................................................................................................................. 21
Table 3-1: MIP Creation Criteria ................................................................................................................. 37
Table 3-2: Port and VLAN Eligibility Criteria ............................................................................................... 39

Chapter
1
1.Introduction
Aricent ECFM (Ethernet Connectivity Fault Management) specifies the protocol entities within the
architecture of Virtual Bridged LAN (Local Area Network) that provides the capabilities for detecting,
verifying and isolating connectivity failures in the Virtual Bridged LAN through CC (Continuity Check), LB
(LoopBack) and LT (LinkTrace) protocols for providing complete 802.1ag functionality. Performance
monitoring is done using LM (Loss Measurement), DM (Delay Measurement) functions and TH
(Throughput Measurement).
1.1 Purpose and Scope
This document describes the CLI (Command Line Interface) and SNMP (Simple Network Management
Protocol) configurations of Aricent ECFM to detect, isolate and verify the faults in connectivity in the
ECFM managed links. It also describes the configurations related to Y.1731 related configurations. The
reader is expected to have a basic knowledge of the protocol as a pre-requisite.
1.2 Acronyms and Abbreviations
The acronyms expanded in Table 1-1 are fundamental to the information in this document.
Table 1-1: Acronyms Used in this Document

Acronym Abbreviation
AIS Alarm Indication Signal
bps Bits per second
CBP Customer Bridge Port
CCM Continuity Check Message

ECFM
CFM Connectivity Fault Management
CFM PDU CFM Protocol Data Unit
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
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
MSTP Multiple Spanning Tree Protocol
PDV Packet Delay Variation
PIP Provider Instance Port
PNP Provider Network Port
pps Packets per second
SNMP Simple Network Management Protocol
CHAPTER 1: INTRODUCTION
TST Test
UMC Unique MEG ID Code
VLAN Virtual LAN
VSM Vendor Specific OAM Message
VSP Vendor Specific OAM
VSR Vendor Specific OAM Reply
CLI Command Line Interface
1.3 IEEE 802.1ag and ITU-T Y.1731 Terminology Mapping
The terminologies used for ECFM and Y.1731 features are mapped in the Table 1-2.
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 Maintenance Domain Intermediate Point (MIP)

Point (MIP)
Maintenance Entity Group Identifier (MEG Maintenance Association Identifier (MA ID)
ID)
MEG Level MD Level
1.4 References
[1] ISS CLI User Manual
[2] IEEE Standard P802.1ag/D7.0 – Draft Standard for Virtual Bridged Local
and Metropolitan Area Network.
[3] ITU-T Recommendation Y.1731 (05/2006) – Draft for OAM functions and
mechanisms for Ethernet based networks.

ECFM
1.5 Document Conventions
The terms and typographical conventions used in this document are listed and explained in Table 1-3.
Table 1-3: Conventions
Convention Usage
Arial 10 Bold CLI commands
Arial 10 Italics User inputs for CLI commands
Courier New 10 Regular, CLI command outputs
blue color
Guidelines / Pre-requisites are keyed inside this text box
Output areas specific to the configuration
These topics convey additional information on an associated topic.
The chapters in this document are organized to describe the general ECFM
configurations both through CLI and SNMP interfaces. Each chapter is organized task
based. Packet flow configurations are explained using specific topologies.
1.6 General Configurations
1.6.1 CLI Configurations

Table 1-4 lists the access and exit methods to the various CLI configuration modes.
Table 1-4: General Configurations
Command Mode Access Method Prompt Exit method
User EXEC This is the initial mode iss> The logout method is
to start a session. used.
Privileged EXEC The User EXEC mode iss# To return from the
command enable, is Privileged EXEC
used to enter the mode to User EXEC
Privileged EXEC mode, the disable
mode. command is used.
Global Configuration The Privileged EXEC iss(config)# To return from the
mode command Global Configuration
configure terminal, is mode to Privileged
used to enter the EXEC mode, the
Global Configuration exit/end command
mode is used.
Interface The Global iss(config-if)# To exit to the Global
Configuration Configuration mode Configuration mode,
command interface the exit command is
<interface- used and to exit to

type><interface-id> the Privileged EXEC
is used to enter the mode, the end
Interface Configuration command is used.
mode.
ECFM configuration The global iss(config-ether- To exit the Global
configuration mode ecfm)# configuration mode,
command ethernet the exit command
cfm domain is used is used and to exit to
to enter the ECFM the Privileged EXEC
configuration mode. mode, the end
In this mode, user can command is used.
configure various
parameters applicable
to this domain.
ECFM MEP The interface iss(config-ether- To exit to the
configuration configuration mode mep)# Interface
command ethernet configuration mode,
cfm mep is used to the exit command
enter the ECFM MEP is used and to exit to
configuration mode. the Privileged EXEC
In this mode, user can mode, the end
configure various command is used.
parameters applicable
to this MEP.
1.6.2 SNMP Configurations
Scotty Manager, version 2.1.10 is used for the following SNMP operations:
• MIB load
• Set operation
• Get operation
• Walk operation
1.6.2.1 SNMP Operations
This section describes the various SNMP operations along with syntax and example.
1.6.2.1.1 MIB Load
The MIB Load operation is used to register the MIB files with the SNMP manager.
Syntax: mib load mib_file.mib

Example: To load the ARICENTQ-BRIDGE-MIB.
% mib load fsmsvlan.mib

ECFM
Table 1-5 lists the MIB files that must be loaded in the SNMP manager before issuing any Get/Set
operation.
Table 1-5: MIB Files
MIB Name Object prefix Description
ARICENT-PROP-PBB-MIB fsPbb MIB module for Aricent PBB
AricentMIMst-MIB fsMIMst MIB module for Aricent proprietary
multiple instance MSTP (Multiple
Spanning Tree Protocol).
ARICENTQ-BRIDGE-MIB fsDot1q The VLAN bridge MIB module for
managing virtual bridged LANs(Local
Area Networks), with multiple instance
capability
ARICENT-PBB-MIB fsPbb Initial version of PBB MIB published in
802.1ap.
ARICENT-MIVLAN-EXT-MIB fsMIVlan The multiple instance extension of
VLAN bridge MIB module.
ARICENT-LA-MIB fsLa The proprietary MIB module for Aricent
LA
ARICENT-CFA-MIB If The MIB module for Aricent CFA
VCM-MIB fsVcm The MIB module for the Aricent virtual
context manager
ARICENT-MIStdBRIDGE-MIB fsDot1d This MIB module for standard bridge
MIB with multiple instance capability.
IF-MIB If The MIB module to describe generic
objects for network interface sub-layers.
This MIB is an updated
version of MIB-II's ifTable. This MIB
incorporates the extensions defined in
RFC 1229.
AricentMIVlan-MIB fsMIDot1q This MIB module is for Aricent
proprietory multiple instance VLAN MIB.
P-BRIDGE-MIB dot1d The bridge MIB extension module
managing Priority and Multicast Filtering
defined by IEEE 802.1D-1998 and
including Restricted Group Registration
defined by IEEE 802.1t-2001.
Q-BRIDGE-MIB dot1q The VLAN bridge MIB module
managing Virtual Bridged Local Area
Networks defined by IEEE 802.1Q-
2003, and including Restricted Vlan
Registration defined by IEEE 802.1u-
2001 and Vlan Classification defined by
IEEE 802.1v-2001
ARICENTP-BRIDGE-MIB fsDot1d The bridge MIB extension module with
multiple instance capability for
managing Priority and Multicast Filtering
defined by IEEE 802.1D-1998. This MIB
includes Restricted Group Registration
defined by IEEE 802.1t-2001.
MIB Name Object prefix Description

Aricent-MIRSTP-MIB fsMIRst MIB for multiple instance rapid spanning
tree algorithm and protocol.
ECFM-MIB dot1agCfm MIB for connectivity fault management
module for managing IEEE 802.1ag
ARICENT-ECFM-MIB fsEcfm The proprietary MIB module for Aricent
ECFM.
ARICENT-ECFM-MI-MIB fsMIEcfm The proprietary MIB module for Aricent
ECFM with multiple instance capability
ARICENT-ECFM-Y1731-MI-MIB fsMIY1731 The Proprietary MIB for Aricent ECFM-
Y1731 module with multiple instance
capability.
ARICENT-ECFM-EXT-MI-MIB fsMIEcfmExt The proprietary multiple instance MIB
for extending Aricent ECFM module
with 802.1ah features.
1.6.2.1.2 Set Operation
The Set operation is used to configure a particular value of an object indentified by the indices used in the
operation.
Syntax: % snmpSession set {{ObjectName.Index1.Index2…IndexN DataType ValueToBeSet}}
DataType is an optional argument.
Example:
To set the bridge mode of a switch with Context ID = 1 to Provider Backone I-Component Bridge,
the syntax is:
% snmp0 set {{fsMIVlanBridgeMode.1 providerBackoneICompBridge}}
Where, Index1 = 1 (ContextId)
ValueToBeSet = providerBackoneICompBridge
SNMP session identifier = snmp0
1.6.2.1.3 Get Operation
The Get operation is used to obtain the configured value of an object indentified by the indices used in the
operation.
Syntax: % snmpSession get {{ObjectName.Index1.Index2…IndexN}}
Output: {ObjectIdentifier DataType Value}
Example:
To get the value of bridge mode of a switch with Context ID = 1, the syntax is:
% snmp0 get {{fsMIVlanBridgeMode.1}}
Where, Index1 = 1 (ContextId)
SNMP session identifier = snmp0
The output is:

ECFM
{1.3.6.1.4.1.2076.138.1.1.1.2.1 INTEGER providerBackoneICompBridge}
1.6.2.1.4 Walk Operation
The snmpwalk command is designed to perform a sequence of chained GETNEXT requests. The
command takes a single OID and displays a list of all results which lie within the subtree rooted on this
OID.
Syntax: % snmpSession walk Object TableName {puts $Object}
Output: {ObjectIdentifier DataType Value}
Example:
To view the maintenance end points configured on the bridge.
% snmp0 walk table fsMIEcfmMepMacAddress {puts $table}
Where SNMP session identifier = snmp0
The output is:
{1.3.6.1.4.1.2076.160.1.0.7.1.9.0.1.1.1 {OCTET STRING}
00:01:02:03:04:03}
{1.3.6.1.4.1.2076.160.1.0.7.1.9.0.2.1.2 {OCTET STRING}
00:01:02:03:04:03}
{1.3.6.1.4.1.2076.160.1.0.7.1.9.0.3.1.1 {OCTET STRING}
00:01:02:03:04:03}
1.6.2.2 Interface Range
The Table 1-6 list the sample ranges used in the configuration commands mentioned in this manual. The
header file of the code should be refered for the exact ranges and scalability constants.
Table 1-6: Interface Index Range

Interface Type Minimum Maximum Formula to calculate the maximum value
Value Value
IVR (Inter 1009 1018 SYS_DEF_MAX_PHYSICAL_INTERFACES +
VLAN Routing) LA_MAX_AGG_INTF+
IP_DEV_MAX_L3VLAN_INTF
Tunnel 1019 1038 Max(IVR) + SYS_DEF_MAX_TUNL_IFACES
MPLS (Multi- 1039 1048 Max(Tunnel) + SYS_DEF_MAX_MPLS_IFACES
Protocol Label
Switching)
MPLS tunnel 1049 5124 Max(MPLS) +
SYS_DEF_MAX_MPLS_TNL_IFACES
Loopback 5125 5134 Max(MPLS tunnel) +
SYS_MAX_LOOPBACK_INTERFACES
I-LAN 5135 5194 Max(Loopback) + SYS_DEF_MAX_ILAN_IFACES
Internal 5195 5254 Max(I-LAN) + SYS_DEF_MAX_INTERNAL_IFACES
VIP 5255 5354 Max(Internal) + SYS_DEF_MAX_VIP_IFACES
The values mentioned in the Table 1-6 are calculated as per the scalability constants listed in the Table
1-7.
Table 1-7: Scalability Constants

Constant Name Value Description
1000 Maximum number of physical interfaces
SYS_DEF_MAX_PHYSICAL_INTERFACES present in the system.
8 Maximum number of link aggregated
LA_MAX_AGG_INTF interfaces present in the system.
60 Maximum number of internal LAN
SYS_DEF_MAX_ILAN_IFACES interfaces present in the system.
60 Maximum number of internal interfaces
SYS_DEF_MAX_INTERNAL_IFACES present in the system.
100 Maximum number of VIPs present in the
SYS_DEF_MAX_VIP_IFACES system.
10 Maximum number of L3 VLAN interfaces
IP_DEV_MAX_L3VLAN_INTF present in the system.
20 Maximum number of tunnel interfaces
SYS_DEF_MAX_TUNL_IFACES present in the system.
10 Maximum number of MPLS interfaces
SYS_DEF_MAX_MPLS_IFACES present in the system.
4076 Maximum number of MPLS tunnel
SYS_DEF_MAX_MPLS_TNL_IFACES interfaces present in the system.
10 Maximum number of loopback interfaces
SYS_MAX_LOOPBACK_INTERFACES present in the system.

Chapter
2
2.Product Description
This chapter describes Aricent ECFM and provides an overview of its salient features, such as, MD
(Maintenance Domain), MA (Maintenance Association), Maintenance Point and CFM (Connectivity Fault
Management) messages.
2.1 Ethernet CFM
Aricent 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 CC, LB and LT 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 LB or LT accordingly
to determine and isolate the fault condition.
Aricent ECFM also provides performance monitoring functions for measurement of various performance
parameters in Ethernet point-to-point connections. It also supports measurement 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.
• Defines Maintenance Domains, Maintenance Associations, their constituent Maintenance Points, and
the managed objects required to create and administer them.
• Describes the protocols and procedures used by Maintenance Points to detect and diagnose
connectivity faults within a maintenance domain.

ECFM
CFM Functions are categorized as follows:

• Fault Detection
• Fault Verification
• Fault Isolation
• Fault Notification
• Performance Management
Fault Detection uses Continuity Check Protocol to detect both connectivity failure and unintended
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
MEP’s.
Fault Verification is an administrative actions, typically performed after fault detection. It uses Loop Back
Protocol to perform Fault Verification. An MEP is ordered to transmit unicast LBM message to MEP in an
MA, and the receiving MEP replies (if Target MAC (Media Access Control) 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 AISs (Alarm Indication Signals), which notify and suppress alarms on
fault events, allowing the relevant operators to take appropriate actions.
Performance management is achieved through Frame Loss measurement and Frame Delay
measurement.
2.2 Maintenance Domain
A Maintenance Domain is the network or the part of the network for which faults in connectivity 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
CHAPTER 2: PRODUCT DESCRIPTION
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.
2.3 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).
Figure 2-2 Maintenance Association
Figure 2-2 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. A MA is associated with
more than one VLAN (Virtual LAN), but different MAs cannot share one VLAN in a single Maintenance
Domain (MD).
For Example:
Figure 2-3 Example Maintenance Association

ECFM
Figure 2-3 illustrates 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.
2.4 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 correct 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.
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 Maintenance Domain
and the Primary VID from the Maintenance Association.
2.5 MEP Functions
MEP is capable of initiating and terminating OAM frames for fault management and performance
monitoring.
The following are the MEP functions:
• Periodically transmits multicast or unicast CCMs.
• 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.
• Validates the received PDU.
• Discards the CFM PDUs that are at lower MD level than MEP.
2.6 MHF (MIP Half Function) Functions
• Validates the received PDUs.

• Validates the received CCM PDUs, and builds the MIP CCM Database.
• Responds to LBM PDUs with LBR PDUs.
• Responds to LTM PDUs by forwarding them and responding with LTR PDUs.
2.7 CFM Features
2.7.1 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.
2.7.1.1 Continuity Check Protocol
Aricent 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 conditions 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
2.7.1.2 LoopBack Protocol
Aricent ECFM uses the LB Protocol to support the fault verification functionality. Fault verification is an
administrative action typically performed after fault detection. Operator initiates 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 originating MEP. The MEP records the information received
in the LBR for examination by the operator.
Unicast LBM can be used for the following applications:
1. To verify bi-directional connectivity of an MEP with an MIP or a peer MEP.

ECFM
2. 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:
1. To verify bi-directional connectivity of an MEP with its entire ME.
2.7.1.3 LinkTrace Protocol
Aricent 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 forwarded to the next MP. The originating MEP
accumulates the responses for examination by the operator.
2.7.1.4 Alarm Indication Signal
Aricent 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 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.
AIS frame can be multicast or unicast.
2.7.1.5 Locked Signal (LCK)
Aricent ECFM uses the LCK (Locked Signal) to communicate to its higher-level MEP(s) that the operator
had deliberately interrupted the data-traffic (Higher layer OAM PDUs and Data-frames), to perform some
Out-Of-Service operations. Operator can enable or disable the Out-Of-Service condition on MEP. When
enabled, LCK frames are transmitted to the client-layer MEP in the direction opposite to the peer MEP.
On reception of LCK frames, the client-layer MEP suppresses its fault alarms, which may have been
triggered by the administrative locking of data-traffic at lower-level MEP.
LCK frame can be multicast or unicast.
2.7.1.6 Test Signal (TST)
Aricent ECFM uses the TST (Test Signal) to perform one-way In-Service or Out-Of-Service diagnostics
tests or for verifying bandwidth throughput. Once the Test-Signal operation is initiated, TST frames are
transmitted to the peer MEP. On reception of TST frames, the MEP checks the TST frames for bit errors
and updates the relevant counters to be examined by the operator.
TST frame can be multicast or unicast.
2.7.1.7 Maintenance Communication Channel (MCC)
Aricent ECFM uses the MCC (Maintenance Communication Channel) to support remote management
between a pair of MEPs. On initiation, MCC frames are sent to the peer MEP. The received information in
MCC frame is provided to the registered application.
2.7.1.8 Experimental OAM (EXP)
Aricent ECFM uses the EXP (Experimental OAM) to support Experimental OAM functionalities within an
administrative domain. On initiation, EXP frame is sent to the peer MEP, which in turn can respond with
an EXR (Experimental OAM Reply) frame. The received information in EXP or EXR frame is provided to
the registered application.
2.7.1.9 Vendor Specific OAM (VSP)
Aricent ECFM uses the VSP (Vendor Specific OAM) to support proprietary vendor specific functionalities
within an administrative domain. On initiation, VSP frame is sent to the peer MEP, which in turn can
respond with a VSR (Vendor Specific OAM Reply) frame. The received information in VSP or VSR frame
is provided to the registered application.
2.7.2 Performance Monitoring
Performance monitoring is necessary to detect potential faults and to pro-actively notify an operator or
peer network nodes. Such notification can further be used for protecting traffic and ensuring service
availability and service level agreements. Frame Loss Measurement, Frame Delay Measurement and
Throughput Measurement together constitute performance monitoring
2.7.2.1 Frame Loss Measurement
Aricent ECFM uses the frame loss measurement function to get the value of Frame Loss Ratio; it is
expressed as the percentage of the number of service frames lost divided by the total number of service
frames transmitted.
Frame Loss Ratio = (Number of service frames lost)/ (Total number of service frames transmitted)
Service frames include data-frames and higher layer OAM PDUs.
Loss Measurement is performed by sending frames with ETH-LM information to the peer MEP and by
receiving frames with ETH-LM information from the peer MEP.
Frame Loss Measurement can be performed in following two ways:
• Dual-Ended ETH-LM, using CCM frame with ETH-LM information.
• Single-Ended ETH-LM, using LMM (Loss Measurement Message) and LMR (Loss Measurement
Reply) frame.

ECFM
2.7.2.2 Frame Delay Measurement
Aricent ECFM uses the frame delay measurement function to get the Frame Delay Value; it is expressed
as the time elapsed since the start of transmission of first bit of the frame by the source until the reception
of the last bit by the destination.
These Measurements are performed by sending periodic frames with ETH-DM information to the peer
MEP and by receiving frames with ETH-DM information from the peer MEP.
Frame Delay Measurement can be performed in following ways:
• One-Way DM, using 1DM frame.
• Two-Way DM, using DMM (Delay Measurement Message) and DMR (Delay Measurement Reply)
frame.
2.7.2.3 Frame Delay Variation Measurement
Aricent ECFM uses the frame delay variation measurement function to get IPDV (Inter-Packet Delay
Variation) and PDV (Packet Delay Variation) values. These Measurements are determined by analyzing
the Frame Delay values taken from Frame Delay Rolling Buffer.
2.7.2.4 Through Measurement
Aricent ECFM uses the throughput measurement function to get throughput value in units of bps (bits per
second); it is expressed as the maximum rate in bps at which none of the offered frames are dropped by
the device.
These measurements are performed by sending periodic ETH-LB or ETH-TST bursts to the peer MEP
and receiving ETH-LB and ETH-TST frames from the peer MEP.
Throughput Measurement can be performed in the following ways.
• One-Way TH, using ETH-TST.
• Two-Way TH, using ETH-LB.
Chapter
3
3.Configuring ECFM in Single Instance Mode
The chapter describes the configuration of ECFM and Y.1731 specific features in Aricent ISS.
3.1 Configuration Guidelines
This section describes the configuration guidelines for ECFM and Y.1731 in SI (Single Instance) mode.
1. The following list of commands must be executed in the specified sequence to start and configure the
ECFM and Y.1731 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>
1
Refer the ISSCLIum [1] for description of the commands.

ECFM
• ethernet cfm mep level <level-id> [inward] mpid <mepid> [vlan <vlan-id>] [active]
• exit
• 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
2. The interface type is gigabitethernet and the interface ID needs to be specified as 0/n, where n is the
interface number.
3.2 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, Disabled
TST, AIS, LCK)
ECFM Entities (MD, MA, MEP, MIP) No Entity Configured
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 started.
3.3 Configuring the ECFM Capabilities
This section describes the configuration of ECFM and Y.1731 entities in SI mode.
3.3.1 Configuring Maintenance Domain

This section describes the configuration of the CFM MD at a particular maintenance level.
3.3.1.1 CLI Configurations
To configure MD on the bridge.

1. Login to the privileged EXEC mode.
iss> enable
CHAPTER 3: CONFIGURING ECFM IN SINGLE INSTANCE MODE
To login into the User Exec mode, use guest as the Username and guest123 as the
password. To login to the Privileged mode, use the enable command or login with
username as root and password as admin123.
2. Enter into the global Configuration mode.

iss# configure terminal
3. Configure the domain name and maintenance level.
iss(config)# ethernet cfm domain name TestDomain1 level 7
iss (config-ether-ecfm)#
To delete configured MD
• Enter into the global configuration mode and delete the configured MD.
iss(config)# no ethernet cfm domain name TestDomain1 level 7
User can configure MD name type/format using ethernet cfm domain format name level
command.
iss(config)# ethernet cfm domain format char-string name TestDomain2 level 1
3.3.1.2 SNMP Configurations
• Configure MD on the bridge. [Index: ContextID = 0, MD-Index = 1].

1. Configure the row status as createAndWait.
% snmp0 set {{fsMIEcfmMdRowStatus.0.1 createAndWait}}
2. Configure name as TestDomain1 [Octet value: 54:65:73:74:44:6f:6d:61:69:6e:31] and
maintenance domain level as 7.
% snmp0 set {{fsMIEcfmMdMdLevel.0.1 7}}
% snmp0 set {{fsMIEcfmMdName.0.1 54:65:73:74:44:6f:6d:61:69:6e:31}}
3. Configure the row status as active.
% snmp0 set {{fsMIEcfmMdRowStatus.0.1 active}}
• Delete the configured MD. [Index: ContextID = 0, MD-Index = 1].

% snmp0 set {{fsMIEcfmMdRowStatus.0.1 destroy}}

ECFM
• User can configure MD name type/format using the following Set operations.
% snmp0 set {{fsMIEcfmMdRowStatus.0.1 notInService}}
% snmp0 set {{fsMIEcfmMdFormat.0.1 macAddressAndUint}}
3.3.2 Configuring Maintenance Association
This section describes the configuration of the CFM MA within a particular MD.
The MD must be configured prior to the configuration of MA.
To configure MA
1. Execute the steps given in section 3.3.1.1 for configuring MD
2. Enter into the ECFM configuration mode and configure service at specific VLAN
iss(config-ether-ecfm)# service name CustAssoc1 vlan 101
3. Return to the Global Configuration mode.
iss(config-ether-ecfm)# exit
To delete configured MA
• Enter into the ECFM configuration mode and delete the service within the MD.
iss(config-ether-ecfm)# no service name CustAssoc1
• User can configure ICC (ITU Carrier Code) and UMC (Unique MEGID Code) using service name
icc umc command.
iss(config-ether-ecfm)# service name CustAssoc1 icc icc1 umc umc1 vlan 101
• User can configure MA name type/format using service format name vlan command.
iss(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 configure MA
1. Execute the steps given in section 3.3.1.2 for configuring MD.
2. Configure service at specific VLAN. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1].
• Configure the row status as createAndWait.

% snmp0 set {{fsMIEcfmMaRowStatus.0.1.1 createAndWait}}
• Configure name as CustAssoc1 [Octet value: 43:75:73:74:41:73:73:6f:63:31] and primary VID of
the MA as 101.
% snmp0 set {{fsMIEcfmMaName.0.1.1 43:75:73:74:41:73:73:6f:63:31}}
% snmp0 set {{fsMIEcfmMaPrimaryVlanId.0.1.1 101}}
• Configure the row status as active.
% snmp0 set {{fsMIEcfmMaRowStatus.0.1.1 active}}
To delete configured MA
• Configure the row status as destroy to delete the service within the MD.[Index: ContextID = 0, MD-
Index = 1, MA-Index = 1].
% snmp0 set {{fsMIEcfmMaRowStatus.0.1.1 destroy}}
3.3.3 Configuring Maintenance End Points
This section describes the configuration of the MEP.
The MD and MA must be configured prior to the configuration of the MEP.
To configure MEP
1. Execute the steps given in section 3.3.2.1 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
iss (config-ether-ecfm)# mep crosscheck mpid 5 vlan 101
VLAN-Unaware MEP can be defined without specifying the vlan parameter in the
command
3. Make the port 10 as member port of VLAN 101 and configure the VLAN 101 as active
iss(config)# vlan 101
iss(config-vlan)# ports gigabitethernet 0/10
iss(config-vlan)# vlan active
4. Enter into the interface configuration mode
iss (config)# interface gigabitethernet 0/10
5. Configure MEP on the interface in the MD and MA
iss(configure-if)#ethernet cfm mep level 7 mpid 5 vlan 101

ECFM
In the command inward keyword needs to be specified for up (inward) direction MEP.
Otherwise MEP will be configured as down (outward) direction MEP
6. Enable the configured MEP.
iss(config-if)# ethernet cfm mep level 7 mpid 5 vlan 101 active
To delete MEP
1. Enter into the interface configuration mode and disable the configured MEP
iss(config-if)# no ethernet cfm mep level 7 mpid 5 vlan 101 active
2. Remove the MEP configuration fromm the interface
iss(config-if)# no ethernet cfm mep level 7 mpid 5 vlan 101
3. Return to the global configuration mode
iss(config-if)# exit
• Port (on which the MEP is configured) and VLAN (VLAN with which MEP is associated) must exist
and must be set as UP, and ECFM must be enabled on the port, for starting VLAN Aware MEP
functionality.
• vlan keyword should not be provided with the command for configuration of VLAN-Unaware MEP.
• MEP must be enabled explicitly as MEP is disabled by default.
• User can enter MEP configuration mode by executing ethernet cfm mep level mpid vlan
command. 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.
To configure MEP
1. Execute the steps given in section 3.3.2.2 for configuring the MA to which MEP needs to be
associated.
2. Configure the MEP ID 5 in the corresponding MA-MEP list. [Index: ContextID = 0, MD-Index = 1, MA-
Index = 1, MEP-ID = 5]
% snmp0 set {{fsMIEcfmMaMepListRowStatus.0.1.1.5 createAndWait}}
% snmp0 set {{fsMIEcfmMaMepListRowStatus.0.1.1.5 active}}
3. Configure the Up MEP at the interface 10. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-
ID = 5]
% snmp0 set {{fsMIEcfmMepRowStatus.0.1.1.5 createAndWait}}
% snmp0 set {{fsMIEcfmMepPrimaryVid.0.1.1.5 101}}
% snmp0 set {{fsMIEcfmMepDirection.0.1.1.5 up}}
% snmp0 set {{fsMIEcfmMepIfIndex.0.1.1.5 10}}
% snmp0 set {{fsMIEcfmMepRowStatus.0.1.1.5 active}}

4. Enable the configured MEP. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-ID = 5]
% snmp0 set {{fsMIEcfmMepRowStatus.0.1.1.5 notInService}}
% snmp0 set {{fsMIEcfmMepActive.0.1.1.5 true}}
To delete configured MEP

• Set the MEP row status as destroy. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-ID = 5]
% snmp0 set {{fsMIEcfmMepRowStatus.0.1.1.5 destroy}}
On enabling ECFM, if the MEP is configured as Active, LBM and LTM messages can be transmitted
and received. If Y.1731 feature is enabled, then DM, FL (Frame Loss), TST, AIS, and LCK messages
can also be transmitted and received.
3.3.4 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 3-1 lists the various MIP creation criteria and their description.
Table 3-1: 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.
Maintenance Association - Control of MIP creation criteria is deferred to the
corresponding variable in the enclosing MD.
defer
Default Domain - Control of MIP creation criteria is deferred to the corresponding
variable in the Default MD default MHF criteria.
3.3.4.1.1 Explicit MIP Creation
Explicit MIP can be configured in two ways:

• MIP associated with an MA
• MIP associated with Default Domain

ECFM
MIP associated with an MA

Pre-requisites:
1. MA must be configured at same MD level and VLAN at which MIP is to be configured.
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:
1. Set the default MD level corresponding to the VLAN in Default MD table.
iss(config)# ethernet cfm default-domain vlan 101 level 7
2. Execute the steps given in section 3.3.3.1 to configure an Up direction MEP for the level 7 and VLAN
101.
3. Set the MIP creation criteria. Refer Table 3-1 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.
• Set the MIP creation criteria parameter to default for an MA
iss(config)#ethernet cfm domain name TestDomain1 level 7
iss(config-ether-ecfm)#service name CustAssoc1 vlan 101 mip-creation-criteria default
OR
• Set the MIP creation criteria to defer for an MA and to default for an MD.
iss(config-ether-ecfm)# set mip-creation-criteria default
iss(config-ether-ecfm)# service name CustAssoc1 vlan 101 mip-creation-criteria defer
4. Entert the interface configuration mode and configure an MIP at specified maintenance level and
VLAN on an interface.
iss(config)# interface gigabitethernet 0/2
iss(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 direction 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
iss(config)# ethernet cfm default-domain vlan 101 level 7 mip-creation-criteria default

iss(config-if)#ethernet cfm mip level 7 vlan 101 active
OR
• Set the parameters such as MD level and MIP creation criteria required for MIP creation at any VLAN.
iss(config)#ethernet cfm default-domain global level 7 mip-creation-criteria default
iss(config-if)#ethernet cfm mip level 7 vlan 101 active
3.3.4.1.2 Implicit MIP Creation
Implicit MIP can be configured when:

• The bridge is initialized.
• MEP is created or deleted on VLAN x on a bridge port.
• A change occurs in the default MD managed object.
• 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 3-2: Port and VLAN Eligibility Criteria

Condition Eligible Port(s) and VLAN(s)
Port - Ports that are not a part of port channel.
VLAN(s) - VLAN(s) which are created in the system and are associated
Bridge initialization with some ports.
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
MEP creation or deletion port.
Port – Ports that are not part of port channel.
VLAN(s) - VLAN(s) with which MA is associated and is associated with
MA creation or deletion some ports.
Port - Ports that are not part of port channel.
Change in Default MD VLAN - VLAN with which Default MD is associated.
Port - Ports that are not a part of port channel.
Change in Default VLAN(s) - VLAN(s) which are created in the system and are associated
Default MD 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.

ECFM
For a particular port p and VLAN x (refer the Table 3-2), MIP creation is evaluated as follows:
1. Determine eligible MD levels for VLAN x based on:
• The MD level of each of the MA that includes VLAN x.
• The Default MD level corresponding to VLAN x.
2. Determine, from the eligible MD levels, a lowest MD level d which satisfies the following condition:
• There is no MP configured on the bridge port p and VLAN x at MD level d or MD level greater than
d.
3. Check the MIP creation criteria (refer Table 3-1) to determine whether an MIP is to be created or not.
MIP creation criteria is taken from:

• MA, if there exists an MA that includes VLAN x and has at least one Up MEP configured on some
bridge port.
• MD, if there exists an MA that includes VLAN x, has at least one Up MEP configured 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.
• 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.
iss(config)# ethernet cfm mip dynamic evaluation
2. Set interfaces 1 and 2 as up.
iss(config)#no shutdown
iss(config)#exit
iss(config)#no shutdown
iss(config)#exit
3. Create VLANs and make interfaces 1 and 2 as member ports of this VLANs.
iss(config)#vlan 1
iss(config-vlan)# ports gigabitethernet 0/1-2
iss(config)#exit
iss(config)#vlan 2
iss(config)#exit
4. Change the global Default MD level as 7 and MIP creation criteria as default.
iss(config)#ethernet cfm default-domain global level 7 mip-creation-criteria default
To verify whether four MIPs are created

• Display details of all the configured MIPs.
iss# show ethernet cfm maintenance-point local
---------------------------------------------------------------------------
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
For starting MIP functionality, Port (on which the MIP is configured) and VLAN (VLAN with which MIP is
associated) must exist and must be UP and ECFM must be enabled on that Port.
3.3.4.2.1 Explicit MIP Creation
Explicit MIP can be configured in the following two ways:

• MIP associated with an MA
• MIP associated with Default Domain
MIP associated with an MA
1. Set the MD level corresponding to the VLAN in Default MD table at which MIP is to be created.[Index:
ContextID = 0, VlanID = 101]
% snmp0 set {{fsMIEcfmDefaultMdLevel.0.101 7}}
2. Execute the steps given in section 3.3.3.2 to configure an Up direction MEP for the MD level 7and
VLAN 101.
3. Configure the MIP creation criteria parameter.
• Set the MIP creation criteria parameter to default for MA. [Index: ContextID = 0, MD-Index = 1,
MA-Index = 1]
% snmp0 set {{fsMIEcfmMaRowStatus.0.1.1 notInService}}

ECFM
% snmp0 set {{fsMIEcfmMaMhfCreation.0.1.1 defMHFdefault}}

OR
• Set the MIP creation criteria parameter to defer for MA and default for MD.
[Index: ContextID = 0, MD-Index = 1]
% snmp0 set {{fsMIEcfmMdRowStatus.0.1 notInService}}
% snmp0 set {{fsMIEcfmMdMhfCreation.0.1 defMHFdefault}}
[Index: ContextID = 0, MD-Index = 1, MA-Index = 1]

% snmp0 set {{fsMIEcfmMaMhfCreation.0.1.1 defMHFdefer}}
4. Configure MIP at VLAN 101 and MD level 7. [Index: Interface Number = 2, MD-level = 7, VlanID =
101]
% snmp0 set {{fsMIEcfmMipRowStatus.2.7.101 createAndGo}}
% snmp0 set {{fsMIEcfmMipRowStatus.2.7.101 active}}
MIP associated with Default Domain
• Set the parameters such as MD level and MIP creation criteria, required for the MIP creation for a
VLAN.
1. Configure Default MD table [Index: ContextID = 0, VlanID = 101]
% snmp0 set {{fsMIEcfmDefaultMdLevel.0.101 7}}
% snmp0 set {{fsMIEcfmDefaultMdMhfCreation.0.101 defMHFdefault}}
2. Configure MIP at MD Level 7, VLAN 101 and interface 1. [Index: Interface Number = 1, MD-level
= 7, VlanID = 101]
OR
• Set the parameters such as MD level and MIP creation criteria, required for MIP creation at any
VLAN.
1. Configure default MD scalar [Index: ContextID = 0]
% snmp0 set {{fsMIEcfmDefaultMdDefMhfCreation.0 defMHF:1 default}}
% snmp0 set {{fsMIEcfmDefaultMdDefLevel.0 7}}
2. Configure MIP at MD Level 7, VLAN 101 and interface 1. [Index: Interface Number = 1, MD-level
= 7, VlanID = 101]
3.3.4.2.2 Implicit MIP Creation
To create MIP(s) based on trigger 3 (A change that occurs in the Default MD):
1. Enable the implicit MIP evaluation and creation. [Index: ContextID = 0]
% snmp0 set {{fsMIEcfmMipDynamicEvaluationStatus.0 true}}
2. Set interfaces 1 and 2 as up.

[Index: Interface Number = 1]
% snmp0 set {{ifMainAdminStatus.1 up}}
% snmp0 set {{fsVcId.1 0}}
% snmp0 set {{fsVcIfRowStatus.1 active}}

3. Create VLAN 101 and make interfaces 1 and 2 as member ports of this VLAN.
[Index: ContextID = 0, VlanId=101]
% snmp0 set {{fsDot1qVlanStaticRowStatus.0.101 createAndWait}}
[Index: ContextID = 0, VlanId=101, Interface Number = 1]

% snmp0 set {{fsDot1qVlanStaticPort.0.101.1 addTagged}}


% snmp0 set {{fsDot1qVlanStaticRowStatus.0.101 active}}
4. Change the default MD default level as 7 and MIP creation criteria as default. [Index: ContextID = 0]
% snmp0 set {{fsMIEcfmDefaultMdDefMhfCreation.0 defMHFdefault}}
To verify whether four MIPs are created

• Walk the table fsMIEcfmMipTable.
% snmp0 walk x fsMIEcfmMipTable {puts $x}
{1.3.6.1.4.1.2076.160.1.1.6.1.4.3.7.1 INTEGER true}

ECFM
{1.3.6.1.4.1.2076.160.1.1.6.1.4.3.7.2 INTEGER true}

{1.3.6.1.4.1.2076.160.1.1.6.1.4.4.7.1 INTEGER true}
{1.3.6.1.4.1.2076.160.1.1.6.1.4.4.7.2 INTEGER true}
{1.3.6.1.4.1.2076.160.1.1.6.1.5.3.7.1 INTEGER active}
{1.3.6.1.4.1.2076.160.1.1.6.1.5.3.7.2 INTEGER active}
{1.3.6.1.4.1.2076.160.1.1.6.1.5.4.7.1 INTEGER active}
{1.3.6.1.4.1.2076.160.1.1.6.1.5.4.7.2 INTEGER active}
3.3.5 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.
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.
iss(config)# ethernet cfm associate vlan-id 1,2,3 primary-vlan-id 7.
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.
iss(config)# no ethernet cfm associate vlan-id 2,3 primary-vlan-id 7.
• One VLAN cannot be associated with more than one Primary VLAN only.
• VLAN and Primary VLAN cannot be the same.
• Associate a set of VLANs 1,2,3 to a Primary VLAN 7

[Index: ContextID = 0, VlanId = 1]
% snmp0 set {{fsMIEcfmVlanRowStatus.0.1 createAndWait}}
% snmp0 set {{fsMIEcfmVlanPrimaryVid.0.1 7}}
% snmp0 set {{fsMIEcfmVlanRowStatus.0.1 active}}

• Disassociate VLANs 2 and 3 from a Primary VLAN 7.

% snmp0 set {{fsMIEcfmVlanRowStatus.0.2 destroy}}
% snmp0 set {{fsMIEcfmVlanRowStatus.0.3 destroy}}
3.3.6 Enabling Ethernet CFM
When Aricent ISS 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).
To enable ECFM
1. Enter into the global configuration mode
2. Enable CFM processing globally
iss(config)# ethernet cfm enable
3. Return to the privileged EXEC mode.
iss(config)# exit
To disable ECFM
• Enter into the global configuration mode and disable CFM processing globally
iss(config)# no ethernet cfm enable
• Enable CFM processing globally.[Index: ContextID = 0]

% snmp0 set {{fsMIEcfmModuleStatus.0 enabled}}
• Disable CFM processing globally. [Index: ContextID = 0]

ECFM
% snmp0 set {{fsMIEcfmModuleStatus.0 disabled}}
3.3.7 Enabling ECFM on an Interface
When Aricent ISS 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 interface, where
the CFM entities are configured, and all the ECFM entities must be configured (MD, MA, MEP and MIP).
To enable ECFM on an interface

On enabling the ECFM, if the MEP is configured as active, LoopBack (LBM) and LinkTrace (LTM)
messages can be transmitted and received.
3. Enter into the interface configuration mode

4. Enable CFM processing on an interface
iss(config-if)# ethernet cfm enable
To disable ECFM on an interface

• Enter into the interface configuration mode and disable CFM processing on an interface
iss(config-if)# no ethernet cfm enable
• Enable ECFM at interface 1. [Index: Interface Number = 1]

% snmp0 set {{fsMIEcfmPortModuleStatus.1 enabled}}
• Disable ECFM at interface 1. [Index: Interface Number = 1].

% snmp0 set {{fsMIEcfmPortModuleStatus.1 disabled}}
3.3.8 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.
To globally enable Y.1731

3. Enable Y.1731 processing globally
iss(config)# ethernet cfm y1731 enable
4. Return to the privileged EXEC mode.
iss(config)# exit
To globally disable Y.1731

• Enter into the global configuration mode and disable Y.1731 processing globally.
iss(config)# no ethernet cfm y1731 enable
• Enable Y.1731 processing globally [Index: ContextID = 0].

% snmp0 set {{fsMIY1731OperStatus.0 enabled}}
• Disable Y.1731 processing globally [Index: ContextID = 0].

% snmp0 set {{fsMIY1731OperStatus.0 disabled}}
3.3.9 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.

ECFM
To enable Y.1731 on an interface

2. Enter into the interface configuration mode.
3. Enable ECFM processing on the interface.
iss(config-if)# ethernet cfm enable
4. Enable Y.1731 processing on the interface.
iss(config-if)# ethernet cfm y1731 enable
To disable Y.1731 on an interface

• Enter into the interface configuration mode and disable Y.1731 processing on the interface.
iss(config-if)# no ethernet cfm y1731 enable
On Enabling the Y.1731, if the MEP is configured as active, LoopBack (LBM/LBR), LinkTrace
(LTM/LTR), Test (TST), Alarm Indication Signal (AIS), Lock (LCK), One-Way Delay Measurement
(1DM), Two-Way Delay Measurement (DMM/DMR), Single-ended Loss Measurement (LMM/LMR),
Dual-ended Loss Measurement messages can also be transmitted and received.
• Enable Y.1731 at an interface. [Index: Interface Number = 1].

% snmp0 set {{fsMIEcfmPortModuleStatus.1 enabled}}
% snmp0 set {{fsMIY1731PortOperStatus.1 enabled}}
• Disable Y.1731 at an interface. [Index: Interface Number = 1]

% snmp0 set {{fsMIY1731PortOperStatus.1 disabled}}
3.3.10 Enabling Ethernet CCM Offload

By default, CCM offloading is in disabled state, that is,. it does not generate or receive the CCM PDU(s)
through hardware.
To enable CCM offloading


2. Enable CCM offloading on all the MEPs
iss(config)# ethernet cfm offload
To disable CCM offloading

• Enter into the global configuration mode and disable CCM offloading on all the MEPs
iss(config)# no ethernet cfm offload
CCM Offloading can be enabled on MEP also using set ethernet cfm offload command
• Enable CCM offloading on all the MEPs [Index: ContextID = 0].

% snmp0 set {{fsMIEcfmGlobalCcmOffload.0 enabled}}
• Disable CCM offloading on all the MEPs [Index: ContextID = 0].

% snmp0 set {{fsMIEcfmGlobalCcmOffload.0 disabled}}
Enable CCM offloading on a particular MEP: [Index: ContextID = 0, MD-Index = 1, MA-Index = 1,

MEP-ID = 5]
% snmp0 set {{fsMIEcfmMepCcmOffload.0.1.1.5 enabled}}
3.3.11 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.
To configure and enable CCM

1. Execute the steps given in section 3.3.3.1 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.
iss(config)# ethernet cfm cc level 1 vlan 101 interval ten-ms
3. Enable the CC functionality.
iss(config)# ethernet cfm cc enable level 1 vlan 101

ECFM
4. Return to the Privileged EXEC Mode.

iss(config)# exit
Set and enable CC parameters for more than one domain levels and VLANs.
Example: ethernet cfm cc level 1-3 vlan 101-105 interval ten-ms
or
ethernet cfm cc level 1,2,3 vlan 101,102,103,104,105 interval ten-ms
To reset CC transmission interval

• Enter into the global configuration mode and reset the CC transmission interval to default interval
(1second).
iss(config)# no ethernet cfm cc level 1 vlan 101.
To disable CC transmission
• Enter into the global configuration mode and disable CC transmission on specified level and VLAN.
iss(config)# no ethernet cfm cc enable level 1 vlan 101
• For VLAN-UnAware MEPs, vlan keyword must not be provided with the command.
• ECFM should be enabled for the successful CCMs transmission.
• By default, CCM messages are multicast and their role is Fault Management.
• MEP, at specified level and VLAN, must be enabled for successful CCM
transmission.
• When Y.1731 is enabled, user has to explicitly enable CCM transmission in an ME.
To configure and enable CCM

1. Execute the steps given in section 3.3.3.2 for configuring MEP before configuring and enabling the CC
transmission parameters.
2. Set the CC parameter (interval). [Index: ContextID = 0, MD-Index = 1, MA-Index = 1]
% snmp0 set {{fsMIEcfmMaCcmInterval.0.1.1 interval10ms}}
3. Enable the CC functionality:
• Individually on an MEP [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-Index = 5]:
% snmp0 set {{fsMIEcfmMepCciEnabled.0.1.1.5 true}}
OR
• On an MA to enable CC transmission status on all the MEPs associated with the MA. [Index:
ContextID = 0, MD-Index = 1, MA-Index = 1]
% snmp0 set {{fsMIY1731MeRowStatus.0.1.1 notInService}}
% snmp0 set {{fsMIY1731MeCciEnabled.0.1.1 true}}
% snmp0 set {{fsMIY1731MeRowStatus.0.1.1 active}}
To disable CC functionality
• Disable CC transmission:
• Individually on an MEP [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-Index = 5]:
% snmp0 set {{fsMIEcfmMepCciEnabled.0.1.1.5 false}}
• On an MA. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1]
% snmp0 set {{fsMIY1731MeCciEnabled.0.1.1 false}}
3.3.12 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.
To configure and enable crosschecking

1. Execute the steps given in section 3.3.2.1 for configuring MA before enabling the crosschecking.
2. Enter into the global configuration mode and set the crosscheck parameter (start-delay)
iss(config)# ethernet cfm mep crosscheck start-delay 3
3. Enable the crosschecking functionality.
iss# ethernet cfm mep crosscheck enable level 1,2 vlan 101
To reset the crosscheck start delay

• Enter into the global configuration mode and reset the crosscheck start-delay to default delay 3.
iss(config)# no ethernet cfm mep crosscheck start-delay.
To disable crosschecking
• Enter into the global configuration mode and disable crosschecking at a specified level and VLAN.

ECFM
iss(config)# ethernet cfm mep crosscheck disable level 1,2 vlan 101.
For VLAN-UnAware MEPs, vlan keyword must not be provided with the command.
To configure and enable crosschecking

1. Execute the steps given in section 3.3.2.2 for configuring MAbefore enabling the crosschecking.
2. Set the crosscheck parameter (that is, start-delay). [Index: ContextID = 0]
% snmp0 set {{fsMIEcfmCrosscheckDelay.0 3}}
3. Enable the crosschecking functionality. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1]
% snmp0 set {{fsMIEcfmMaCrosscheckStatus.0.1.1 enabled}}
To disable crosschecking
• Disable crosschecking functionality. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1]
% snmp0 set {{fsMIEcfmMaCrosscheckStatus.0.1.1 disabled}}
3.3.13 Configuring and Enabling LoopBack Messages
After configuring and enabling LoopBack messages, every MEP (if MD, MA and MEP are configured) can
transmit LoopBack messages.
To configure loopback message

• Execute the steps given in section 3.3.3.1 for configuring MEP respectively before sending the LBMs.
For ECFM compliant loopback feature

• Execute the steps given in section 3.3.6.1 to enable ECFM.
• Send the loopback messages to the MEP destination.
iss# 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
iss#
For Y.1731 compliant loopback feature

• Execute the steps mentioned in section 3.3.8.1 to enable Y.1731.
• Send the loopback messages to the MEP destination.
iss# 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.
64 bytes from 00:02:02:03:04:03: seq_no=0 time=80 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
iss#
The above mentioned steps are only for initiating the loopback message. User may
not get the same output. To get the same output, target entity also needs to be
configured.
• For sending Loopback messages to a MEP destination using MEPID.

Example: ping ethernet mpid 101 level 7 vlan 101 count 3
• Mac Address of the 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.
• In ECFM, “count”, if not provided, number of loopback messages to send is considered as
one.
• In case Y.1731 is enabled,
1. “count” and “deadline” keyword, if not provided, assumes infinite number of
loopback messages to send.
2. If user does not provide target MPID and MAC Address, it will be treated as multicast
loopback messages.
3. 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:
iss(config-ether-mep)# set params capability enable ping
iss(config)# ethernet cfm mep-capability enable level 7 vlan 101 ping

ECFM
To configure loopback message

• Execute the steps given in section 3.3.3.2 for configuring MEP before sending the LBMs.
For ECFM compliant loopback feature

• Send the loopback messages to the MEP destination. [Index: ContextID = 0, MD-Index = 1, MA-Index
= 1, MEP-Index = 5]
1. Set the destination MAC address
%snmp0 set {{fsMIEcfmMepTransmitLbmDestMacAddress.0.1.1.5 00:02:02:03:04:03 }}
2. Set the number of LBM count (messages)
%snmp0 set {{fsMIEcfmMepTransmitLbmMessages.0.1.1.5 1}}
3. Set the LBM Status as transmit
%snmp0 set {{fsMIEcfmMepTransmitLbmStatus.0.1.1.5 transmit}}
For Y.1731 compliant loopback feature

• Execute the steps mentioned in section 3.3.8.2 to enable Y.1731.
• Send the Loopback messages to the MEP destination. [Index: ContextID = 0, MD-Index = 1, MA-Index
= 1, MEP-Index = 5]
1. Set the destination MAC address
%snmp0 set {{fsMIY1731MepTransmitLbmDestMacAddress.0.1.1.5 00:02:02:03:04:03 }}
2. Set the number of LBM count (messages)
%snmp0 set {{fsMIY1731MepTransmitLbmMessages.0.1.1.5 1}}
3. Set the LBM status as start
%snmp0 set {{fsMIY1731MepTransmitLbmStatus.0.1.1.5 start}}
In case Y.1731 is enabled, MEP at specified level and VLAN must be enabled for a loopback
transaction. The loopback (ping) capability can be enabled using the following steps
Example: [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-Index = 5]
• % snmp0 set {{fsMIY1731MepRowStatus.0.1.1.5 notInService}}
• % snmp0 set {{fsMIY1731MepLoopbackCapability.0.1.1.5 enabled}}
• % snmp0 set {{fsMIY1731MepRowStatus.0.1.1.5 active}}
3.3.14 Configuring and Enabling Linktrace Messages
After configuring and enabling LTMs, every MEP (if MD, MA and MEP are configured) can transmit LTMs.
To configure linktrace message

• Execute the steps given in section 3.3.3.1 to configure MEP before sending the LTMs.
For ECFM compliant linktrace feature

• Enable linktrace caching on the device.
iss# config terminal
iss(config)# ethernet cfm traceroute cache
iss(config)# end
• Send the LTM to an MEP destination.
iss# 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
iss#
For Y.1731 compliant linktrace feature

• Execute the steps in section 3.3.8.1 to enable Y.1731.
• Enable linktrace caching on the device.
iss# config terminal
iss(config)# end
• Send theLTMs to the MEP destination.
iss# traceroute ethernet mac 00:02:02:03:04:02 level 7 vlan 101
Traceroute to Macaddress 00:02:02:03:04:02 in domain meg1 at level 7
with vlanId 101
---------------------------------------------------------------------------

ECFM

---------------------------------------------------------------------------
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 mentioned steps are only for initiating the linktrace message. User may
configured.
• 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.
• 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.
To configure linktrace message

• Execute the steps given in section 3.3.3.2 to configure MEP before sending the LTMs.
For ECFM compliant linktrace feature

• Enable linktrace caching on the device.[Index: ContextID = 0]
%snmp0 set {{ fsMIEcfmLtrCacheStatus.0 enabled}}
• Send the LTM to an MEP destination. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-Index
= 5]
% snmp0 set {{fsMIEcfmMepTransmitLtmTargetIsMepId.0.1.1.5 false}}
% snmp0 set {{fsMIEcfmMepTransmitLtmTargetMacAddress.0.1.1.5 00:02:02:03:04:0a}}
% snmp0 set {{fsMIEcfmMepTransmitLtmTtl.0.1.1.5 32}}
% snmp0 set {{fsMIEcfmMepTransmitLtmStatus.0.1.1.5 transmit}}
• View the information received in the LTR.
% snmp0 walk x fsMIEcfmLtrTable {puts $x}
{1.3.6.1.4.1.2076.160.1.0.8.1.3.0.1.1.5.2.1 Unsigned32 31}
{1.3.6.1.4.1.2076.160.1.0.8.1.4.0.1.1.5.2.1 INTEGER false}

{1.3.6.1.4.1.2076.160.1.0.8.1.5.0.1.1.5.2.1 INTEGER true}
{1.3.6.1.4.1.2076.160.1.0.8.1.6.0.1.1.5.2.1 {OCTET STRING}
00:01:02:03:04:01:00:0A}
{1.3.6.1.4.1.2076.160.1.0.8.1.7.0.1.1.5.2.1 {OCTET STRING}
00:02:02:03:04:01:00:0A}
{1.3.6.1.4.1.2076.160.1.0.8.1.8.0.1.1.5.2.1 INTEGER rlyHit}
{1.3.6.1.4.1.2076.160.1.0.8.1.9.0.1.1.5.2.1 INTEGER 0}
{1.3.6.1.4.1.2076.160.1.0.8.1.10.0.1.1.5.2.1 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.11.0.1.1.5.2.1 {OBJECT IDENTIFIER} 0}
{1.3.6.1.4.1.2076.160.1.0.8.1.12.0.1.1.5.2.1 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.13.0.1.1.5.2.1 INTEGER 0}
{1.3.6.1.4.1.2076.160.1.0.8.1.14.0.1.1.5.2.1 {OCTET STRING}
00:00:00:00:00:00}
{1.3.6.1.4.1.2076.160.1.0.8.1.15.0.1.1.5.2.1 INTEGER 0}
{1.3.6.1.4.1.2076.160.1.0.8.1.16.0.1.1.5.2.1 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.17.0.1.1.5.2.1 INTEGER egrOK}
{1.3.6.1.4.1.2076.160.1.0.8.1.18.0.1.1.5.2.1 {OCTET STRING}
00:02:02:03:04:0A}
{1.3.6.1.4.1.2076.160.1.0.8.1.19.0.1.1.5.2.1 INTEGER 1}
{1.3.6.1.4.1.2076.160.1.0.8.1.20.0.1.1.5.2.1 {OCTET STRING}
53:6C:6F:74:30:2F:31:30}
{1.3.6.1.4.1.2076.160.1.0.8.1.21.0.1.1.5.2.1 {OCTET STRING} 1F:00:04:00:02}
For Y.1731 compliant linktrace feature

• Execute the steps in section 3.3.8.2 to enable Y.1731, then enable linktrace caching and send the
LTM.
3.3.15 Configuring and Enabling Test Messages
This section describes the steps to configure and enable the transmission and reception of TST PDU by
an MEP.
To configure and enable test messages

1. Execute the steps given in section 3.3.3.1 to configure MEP before sending the test messages.
2. Execute the steps given in section 3.3.8.1 to enable ECFM and Y.1731 for Y.1731 test message
feature.
3. Send the TST message to an MEP using destination’s MAC address.
iss# ethernet cfm test mac 00:02:02:03:04:03 level 7 vlan 101 count 5

ECFM
TST to 00:02:02:03:04:03 from 00:01:02:03:04:03 with 33(64) bytes of data.

60 bytes to 00:02:02:03:04:03: seq_no=0
60 bytes to 00:02:02:03:04:03: seq_no=1
60 bytes to 00:02:02:03:04:03: seq_no=2
60 bytes to 00:02:02:03:04:03: seq_no=3
60 bytes to 00:02:02:03:04:03: seq_no=4
--- 00:02:02:03:04:03 test statistics ---
packets sent = 5 with prbs signal without crc32 pattern
iss#
• For sending a Test message to an MEP using destination’s MEPID.

Example: ethernet cfm test mpid 2 level 6 vlan 5 count 5
• MAC Address of MEP with specified target mpid must be learned prior to the execution of
the command.
• If the user does not provide target MPID and MAC Address, it will be treated as multicast
TST messages.
• ECFM and Y.1731 should be enabled for the successful Test message transmission.
• count and deadline keyword, if not provided, assumes infinite number of test messages to
send.
To configure and enable test messages

1. Execute the steps given in section 3.3.3.2 to configure MEP before sending the test messages.
2. Execute the steps given in section 3.3.8.2 to enable ECFM and Y.1731 for Y.1731 test message
feature.
3. Send the TST message to an MEP using destination MAC address. [Index: ContextID = 0, MD-Index
= 1, MA-Index = 1, MEP-Index = 5]
%snmp0 set {{fsMIY1731MepTransmitTstDestMacAddress.0.1.1.5 00:02:02:03:04:03 }}
%snmp0 set {{fsMIY1731MepTransmitTstMessages.0.1.1.5 5}}
%snmp0 set {{fsMIY1731MepTransmitTstStatus.0.1.1.5 start}}
MEP at specified level and VLAN must be enabled for a test transaction. The test capability can
be enabled using the following steps
Example: [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-Index = 5]
• % snmp0 set {{fsMIY1731MepRowStatus.0.1.1.5 notInService}}
• % snmp0 set {{fsMIY1731MepTstCapability.0.1.1.5 enabled}}
• % snmp0 set {{fsMIY1731MepRowStatus.0.1.1.5 active}}
3.3.16 Configuring and Enabling Frame Delay Measurement
This section describes the steps to configure and enable the transmission and reception of Frame delay
PDU by an MEP.
Frame Delay can be measured using either of the following methods:
• One-way Frame Delay Measurement
• Two-way Frame Delay Measurement
To configure and enable frame delay measurement

1. Execute the steps given in section 3.3.3.1 to configure MEP before sending the FD messages.
2. Execute the steps given in sections 3.3.8.1 to enable ECFM and Y.1731.
3. Measure frame delay by
• Sending the one-way frame delay message to an MEP using destination MAC address.
iss# ethernet cfm frame delay start type one-way level 7 vlan 101 mac 00:02:02:03:04:03
count 5
OR
• Sending the two-way frame delay message to an MEP using destination MAC address.
iss# ethernet cfm frame delay start type two-way level 7 vlan 101 mac 00:02:02:03:04:03
count 5
To stop frame delay measurement

• Stop the frame delay measurement by:
• Configuring the count or deadline parameter while initiating the delay measurement.
OR
• Using the ethernet cfm frame delay stop type level vlan command.
The above mentioned steps are only for initiating the frame delay message. User
may not get the same output. To get the same output, target entity also needs to be
configured.

ECFM
• For sending a Frame Delay message to an MEP using destination’s MEPID.

Example: ethernet cfm frame delay start type two-way level 7 vlan 101 mpid 2 count 5
the command.
• ECFM and Y.1731 should be enabled for the successful Frame Delay message transmission.
• At a time, MEP can perform only one type of delay measurement.
• count and deadline, if not provided, assumes infinite number of frame delay messages to
send.
• User can view the result of delay measurement using show ethernet cfm frame delay
buffer command.
To configure and enable frame delay measurement

1. Execute the steps given in section 3.3.3.2 to configure MEP before sending the frame delay
messages.
2. Execute the steps given in section 3.3.8.2 to enable ECFM and Y.1731.
3. Measure frame delay by
• Sending the one-way frame delay message to an MEP using destination MAC address. [Index:
ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-Index = 5]
% snmp0 set {{fsMIY1731MepTransmitDmDestIsMepId.0.1.1.5 false}}
% snmp0 set {{fsMIY1731MepTransmitDmDestMacAddress.0.1.1.5 00:02:02:03:04:0a}}
% snmp0 set {{fsMIY1731MepTransmitDmType.0.1.1.5 oneWay}}
% snmp0 set {{fsMIY1731MepTransmitDmMessages.0.1.1.5 5}}
% snmp0 set {{fsMIY1731MepTransmitDmStatus.0.1.1.5 start}}
OR
• Sending the two-way frame delay message to an MEP using destination MAC address. [Index:
% snmp0 set {{fsMIY1731MepTransmitDmDestMacAddress.0.1.1.5 00:02:02:03:04:0a}}
% snmp0 set {{fsMIY1731MepTransmitDmType.0.1.1.5 twoWay}}
To stop frame delay measurement

• Configuring the number of messages or deadline parameter while initiating the delay
measurement. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-Index = 5]
% snmp0 set {{fsMIY1731MepTransmitDmDeadline.0.1.1.5 10}}
OR
• Configuring the transmit status as stop: [Index: ContextID = 0, MD-Index = 1, MA-Index = 1,
MEP-Index = 5]
% snmp0 set {{fsMIY1731MepTransmitDmStatus.0.1.1.5 stop}}
3.3.17 Configuring and Enabling Frame Loss Measurement
This section describes the steps to configure and enable the transmission and reception of Frame loss
PDU by an MEP.
Frame Loss can be measured using either of the following methods:
• Dual-ended using CCM messages
• Single-ended using LMM/LMR messages
To configure and enable frame loss measurement

1. Execute the steps given in section 3.3.3.1 to configure MEP before sending the frame loss messages.
3. Measure frame loss using
• Single-ended method
• Send the message to an MEP using destination’s MAC address.
iss# ethernet cfm frame loss start level 7 vlan 101 mac 00:02:02:03:04:03 count 5
OR
• Dual-ended method
• Configure the CC unicast MAC address. This is the MAC address of the remote MEP with
which the frame loss is to be measured.
iss(config-ether-mep)# set ccm- mac unicast 00:02:02:03:04:03
iss(config-ether-mep)# end
• Send the message to measure frame loss by setting the role as performance-monitoring.

ECFM
iss(config)# ethernet cfm cc level 7 vlan 101 role performance-monitoring

iss(config)# end
To stop frame loss measurement

• Stop the single-ended frame loss measurement by
• Configuring the count or deadline parameter while initiating the loss measurement
OR
• Using the ethernet cfm frame loss stop level vlan command
• Stop dual-ended frame loss measurement by
• Disabling CC transmission
iss(config)# no ethernet cfm cc enable level 7 vlan 101
iss(config)# end
Or
• Changing the CC role to role other than performance monitoring
iss(config)# ethernet cfm cc level 7 vlan 101 role fault-management
iss(config)# end
The above mentioned steps are only for initiating the frame loss message. User may
configured.
• For sending a Frame Loss message to an MEP using destination’s MEPID.

Example: ethernet cfm frame loss start level 7 vlan 101 mpid 2 count 5
the command.
• ECFM and Y.1731 should be enabled for the successful frame loss message transmission.
• At a time, MEP can perform only one type of loss measurement.
• count and deadline, if not provided, assumes infinite number of frame loss messages to
send.
• User can view the result of loss measurement using show ethernet cfm frame loss buffer
command.
• CC Performance monitoring should be enabled on all the MEPs involved in dual-ended frame
loss measurement.
To configure and enable frame loss measurement

1. Execute the steps given in section 3.3.3.2 to configure MEP before sending the frame loss messages.
3. Measure frame loss using
• Single-ended method [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-Index = 5]
• Send the message to an MEP using destination MAC address.
% snmp0 set {{fsMIY1731MepTransmitLmmDestIsMepId.0.1.1.5 false}}
%snmp0 set {{fsMIY1731MepTransmitLmmDestMacAddress.0.1.1.5 00:02:02:03:04:0a}}
% snmp0 set {{fsMIY1731MepTransmitLmmMessages.0.1.1.5 5}}
% snmp0 set {{fsMIY1731MepTransmitLmmStatus.0.1.1.5 start}}
OR
• Dual-ended method
• Configure the CC unicast MAC address. This is the MAC address of the remote MEP with
which the frame loss is to be measured. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1,
MEP-Index = 5]
% snmp0 set {{fsMIY1731MepUnicastCcmMacAddress.0.1.1.5 00:02:02:03:04:0a}}
% snmp0 set {{fsMIY1731MeCcmApplication.0.1.1 ccPerformanceMonitoring}}
% snmp0 set {{fsMIY1731MeCciEnabled.0.1.1 true}}
To stop frame loss measurement

• Stop single-ended frame loss measurement by
• Configuring the number of messages or deadline parameter while initiating the loss measurement.
[Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-Index = 5]
% snmp0 set {{fsMIY1731MepTransmitLmmDeadline.0.1.1.5 10}}
OR
• Configuring the transmit status as stop: [Index: ContextID = 0, MD-Index = 1, MA-Index = 1,
MEP-Index = 5]
% snmp0 set {{fsMIY1731MepTransmitLmmStatus.0.1.1.5 stop}}
• Stop dual-ended frame loss measurement by:

ECFM
• Disabling CC transmission. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1]

% snmp0 set {{fsMIY1731MeCciEnabled.0.1.1 false}}
OR
• Changing the CC role to role other than performance monitoring. [Index: ContextID = 0, MD-Index
= 1, MA-Index = 1]
% snmp0 set {{fsMIY1731MeCcmApplication.0.1.1 ccFaultManagement}}
3.3.18 Configuring and Enabling Alarm Indication signal Messages
This section describes the steps to configure and enable the transmission of AIS PDU by an MEP.
To configure and enable AIS message

1. Execute the steps given in section 3.3.3.1 to configure MEP before sending the AIS messages.
3. Configure client layer level.
iss (config-ether-ecfm)# client-layer-level 6
iss# 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.
iss(config-if)# ethernet cfm mep level 3 inward mpid 4 vlan 5 active
iss(config-ether-mep)# set ais enable
• AIS capability can also be enabled using ethernet cfm mep-capability enable level 3 vlan
5 ais command
• Client layer level must be configured before enabling AIS capability.
• AIS can be send as unicast messages by configuring its unicast MAC address using set
client-layer-mac ais unicast command. (This command runs in ECFM Mep configuration
Mode.)
Example: set client-layer-mac ais unicast 00:01:02:03:04:06
To configure and enable AIS message

1. Execute the steps given in section 3.3.3.2 to configure MEP at level 3 and VLAN 101 before sending
the AIS messages.
3. Configure client layer level. [Index: ContextID = 0, MD-Index = 1]
% snmp0 set {{fsMIY1731MegRowStatus.0.1 notInService}}
% snmp0 set {{fsMIY1731MegClientMEGLevel.0.1 6}}
% snmp0 set {{fsMIY1731MegRowStatus.0.1 active}}
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. [Index: ContextID = 0, MD-Index = 1, MA-
Index = 1, MPID = 5]
% snmp0 set {{fsMIY1731MepRowStatus.0.1.1.5 notInService}}
% snmp0 set {{fsMIY1731MepAisCapability.0.1.1.5 enabled}}
% snmp0 set {{fsMIY1731MepRowStatus.0.1.1.5 active}}
• Configure unicast MAC address to send AIS as unicast messages

Example:
% snmp0 set {{fsMIY1731MepAisClientMacAddress.0.1.1.5 00:02:02:03:04:0a}}
3.3.19 Configuring and Enabling Lock Messages
This section describes the steps to configure and enable the transmission of LCK PDU by an MEP.
To configure and enable LCK message

1. Execute the steps given in section 3.3.3.1 to configure MEP before sending the LCK messages.

ECFM
2. Execute the steps given in section 3.3.9.1 to enable ECFM and Y.1731 on the interface at which MEP
is configured.
3. Configure client layer level.
iss (config-ether-ecfm)# client-layer-level 6
iss# end
4. Enable LCK capability on the MEP, so that when any defect occurs, the MEP starts transmitting the
LCK to all the MEP(s) configured at the client layer level.
iss(config-ether-mep)# set out-of-service enable
• Client layer level must be configured before enabling LCK capability.

• LCK can be send as unicast messages by configuring its unicast MAC address using set
client-layer-mac lck unicast command. (This command runs in ECFM Mep configuration
Mode.)
Example: set client-layer-mac lck unicast 00:01:02:03:04:06
To configure and enable LCK message

1. Execute the steps given in section 3.3.3.2 to configure MEP at level 3 and VLAN 101 before sending
the LCK messages.
2. Execute the steps given in section 3.3.9.2 to enable ECFM and Y.1731 on the interface at which MEP
is configured.
3. Configure client layer level. [Index: ContextID = 0, MD-Index = 1]
4. Enable LCK capability on the MEP, so that when any defect occurs, the MEP starts transmitting the
LCK to all the MEP(s) configured at the client layer level. [Index: ContextID = 0, MD-Index = 1, MA-
Index = 1, MEP-Index = 5]
% snmp0 set {{fsMIY1731MepOutOfService.0.1.1.5 true}}
• Lck can be send as unicast messages by configuring its unicast MAC address using the
following step
Example:
% snmp0 set {{fsMIY1731MepLckClientMacAddress.0.1.1.5 00:02:02:03:04:0a}}
3.3.20 Configuring and Enabling Throughput Measurement

This section describes the steps to configure and enable the Throughput Measurement by an MEP.
Throughput Measurement can be measured using either of the following methods:
• One-way Throughput Measurement
• Two-way Throughput Measurement
To configure and enable throughput measurement

1. Execute the steps given in section 3.3.3.1 to configure MEP before starting throughput measurement.
3. Measure throughput by
• Starting the One-way Throughput Measurement at an MEP using destination MAC address.
iss# ethernet cfm throughput type one-way mac 00:01:02:03:04:04 level 7 vlan 101 count 15
1217600/1.217600, packet size 1522 bytes
--- 00:01:02:03:04:04 one-way throughput statistics ---
final throughput 1200000 / 1.200000, packet size 1500 bytes
transmission rate = 100 pps
OR
• Starting the Two-way Throughput Measurement at an MEP using destination MAC address.
iss# ethernet cfm throughput type two-way mac 00:01:02:03:04:04 level 7 vlan 101 count 15
--- 00:01:02:03:04:04 two-way throughput statistics ---
final throughput 1200000 / 1.200000, packet size 1500 bytes
To stop throughput measurement

• Stop the throughput measurement by configuring the count or deadline parameter while initiating the
throughput measurement.

ECFM
The above mentioned steps are only for initiating the throughput transaction. The
user may not get the same output. To get the same output, target entity also needs to
be configured.
• To start the Throughput transaction at an MEP using destination MEPID, execute the
command,
ethernet cfm throughput type one-way mac 00:01:02:03:04:04 level 7 vlan 101 count 15
• Mac Address of the MEP with specified target “mpid” must be learnt prior to the execution of
the command.
• “count” and “deadline” keyword, if not provided, assumes infinite number of throughput
measurement.
• MEP at specified level and VLAN must be enabled for a two way throughput transaction
which uses loopback functionality. 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:
iss(config-ether-mep)# set params capability enable ping
iss(config)# ethernet cfm mep-capability enable level 7 vlan 101 ping
• MEP at specified level and VLAN must be enabled for a one way throughput transaction
which uses test functionality. The test capability can be enabled using either set params
capability enable test (runs in ECFM MEP configuration mode) or ethernet cfm mep-
capability enable level vlan test (runs in Global Configuration mode)command.
Example:
iss(config-ether-mep)# set params capability enable test
iss(config)# ethernet cfm mep-capability enable level 7 vlan 101 test
To configure and enable throughput measurement

1. Execute the steps given in section 3.3.3.2 to configure MEP before starting throughput measurement.
3. Measure throughput by
• Starting the one-way throughput measurement at an MEP using destination MAC address. [Index:
% snmp0 set {{fsMIY1731MepTransmitThType.0.1.1.5 oneWay}}
% snmp0 set {{fsMIY1731MepTransmitThDestIsMepId.0.1.1.5 false}}
% snmp0 set {{fsMIY1731MepTransmitThDestMacAddress.0.1.1.5 00:02:02:03:04:0a}}
% snmp0 set {{fsMIY1731MepTransmitThMessages.0.1.1.5 15}}
% snmp0 set {{fsMIY1731MepTransmitThStatus.0.1.1.5 start}}
OR
• Starting the two-way throughput measurement at an MEP using destination MAC address. [Index:
% snmp0 set {{fsMIY1731MepTransmitThType.0.1.1.5 twoWay}}
% snmp0 set {{fsMIY1731MepTransmitThDestIsMepId.0.1.1.5 false}}
% snmp0 set {{fsMIY1731MepTransmitThDestMacAddress.0.1.1.5 00:02:02:03:04:0a}}
% snmp0 set {{fsMIY1731MepTransmitThMessages.0.1.1.5 15}}
% snmp0 set {{fsMIY1731MepTransmitThStatus.0.1.1.5 start}}
To stop throughput measurement

• Stop the one-way throughput measurement at an MEP. [Index: ContextID = 0, MD-Index = 1, MA-
% snmp0 set {{fsMIY1731MepTransmitThStatus.0.1.1.5 stop}}
• Stop the two-way throughput measurement at an MEP. [Index: ContextID = 0, MD-Index = 1, MA-
% snmp0 set {{fsMIY1731MepTransmitThStatus.0.1.1.5 stop}}
3.3.21 Setting OUI (Organizational Unit Identifier)
This section describes the steps required to configure the OUI globally on a device.
To configure the OUI globally on a device

2. Set the OUI
iss(config)# set ethernet-cfm oui 02:03:04.
Default value corresponds to the first three bytes of the System MAC Address.
3. Return to the Privileged Exec Mode.

iss(config)# exit
To set the OUI to default value

• Enter into the global configuration mode and reset the OUI to default value.
iss(config)# no set ethernet-cfm oui.

ECFM
• Configure the OUI globally on a device. [Index: ContextID = 0]

% snmp0 set {{fsMIEcfmOui.0 aa:bb:cc}}
3.3.22 Enabling LLC Encapsulation on interface
This section describes the steps to enable the CFM PDU encapsulation in LLC header on the specified
port.
To enable LLC encapsulation on a port.

2. Enter into the interface configuration mode.
3. Enable the LLC encapsulation on the port.
iss(config-if)# ethernet cfm llc-encap enable
4. Return to the global configuration mode.
To disable LLC encapsulation

• Enter into the interface configuration mode and disable the ECFM.
iss(config-if)# ethernet cfm llc-encap disable
• Enable the LLC encapsulation on a port. [Index: Interface Number = 1]

% snmp0 set {{fsMIEcfmPortLLCEncapStatus.1 true}}
• Disable the LLC encapsulation on a port. [Index: Interface Number = 1]

% snmp0 set {{fsMIEcfmPortLLCEncapStatus.1 false}}
3.4 Displaying Ethernet CFM Entities
This section describes the viewing of information related to configured ECFM and Y.1731 entities in SI
mode.
ECFM entities are displayed on the Aricent ISS shell. Aricent 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 ]
Ethernet CFM entities can be displayed through

• walk on the entire table
• get of the individual entries
3.4.3 Displaying Maintenance Domain
This section describes the command that is used to display the information (displays the maintenance
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.
• Display the MD configured on the bridge.

iss# 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
• Display the MD configured on the bridge.

% snmp0 walk table fsMIEcfmMdTable {puts $table}
{1.3.6.1.4.1.2076.160.1.0.4.1.2.0.1 INTEGER charString}
{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.1 {OCTET STRING} 6F:70:65:72:31}

ECFM
{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.2 {OCTET STRING} 6F:70:65:72:32}

{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.3 {OCTET STRING} 6F:70:65:72:33}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.1 INTEGER 4}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.2 INTEGER 3}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.3 INTEGER 5}
{1.3.6.1.4.1.2076.160.1.0.4.1.5.0.1 INTEGER defMHFnone}
{1.3.6.1.4.1.2076.160.1.0.4.1.6.0.1 INTEGER sendIdNone}
{1.3.6.1.4.1.2076.160.1.0.4.1.7.0.1 Unsigned32 1}
{1.3.6.1.4.1.2076.160.1.0.4.1.7.0.2 Unsigned32 1}
{1.3.6.1.4.1.2076.160.1.0.4.1.7.0.3 Unsigned32 1}
{1.3.6.1.4.1.2076.160.1.0.4.1.8.0.1 INTEGER active}
{1.3.6.1.4.1.2076.160.1.0.4.1.8.0.2 INTEGER active}
{1.3.6.1.4.1.2076.160.1.0.4.1.8.0.3 INTEGER active}
3.4.4 Displaying Maintenance Association
This section describes the command that is used to display the details (displays the maintenance
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) configured in the system.
• Display the MA configured on the bridge.

iss# 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
• Display the MA configured on the bridge.

% snmp0 walk table fsMIEcfmMaTable {puts $table}
{1.3.6.1.4.1.2076.160.1.0.5.1.2.0.1.1 INTEGER 3}
{1.3.6.1.4.1.2076.160.1.0.5.1.2.0.2.1 INTEGER 4}
{1.3.6.1.4.1.2076.160.1.0.5.1.2.0.4.2 INTEGER 1}
{1.3.6.1.4.1.2076.160.1.0.5.1.3.0.1.1 INTEGER charString}
{1.3.6.1.4.1.2076.160.1.0.5.1.4.0.1.1 {OCTET STRING} 6D:61:6F:70:65:72:31}
{1.3.6.1.4.1.2076.160.1.0.5.1.4.0.2.1 {OCTET STRING} 6D:61:6F:70:65:72:32}
{1.3.6.1.4.1.2076.160.1.0.5.1.4.0.4.2 {OCTET STRING} 6D:61:6F:70:65:72:33}
{1.3.6.1.4.1.2076.160.1.0.5.1.5.0.1.1 INTEGER defMHFdefer}
{1.3.6.1.4.1.2076.160.1.0.5.1.6.0.1.1 INTEGER sendIdDefer}
{1.3.6.1.4.1.2076.160.1.0.5.1.7.0.1.1 INTEGER interval1s}
{1.3.6.1.4.1.2076.160.1.0.5.1.7.0.2.1 INTEGER interval10ms}
{1.3.6.1.4.1.2076.160.1.0.5.1.7.0.4.2 INTEGER interval10min}
{1.3.6.1.4.1.2076.160.1.0.5.1.8.0.1.1 Unsigned32 1}
{1.3.6.1.4.1.2076.160.1.0.5.1.8.0.2.1 Unsigned32 1}
{1.3.6.1.4.1.2076.160.1.0.5.1.8.0.4.2 Unsigned32 1}
{1.3.6.1.4.1.2076.160.1.0.5.1.9.0.1.1 INTEGER active}
{1.3.6.1.4.1.2076.160.1.0.5.1.9.0.2.1 INTEGER active}
{1.3.6.1.4.1.2076.160.1.0.5.1.9.0.4.2 INTEGER active}
3.4.5 Displaying Maintenance Points configured
This section describes the command that is used to display the maintenance points configured in the
system.
• Display the MEPs configured on the bridge.

iss# show ethernet cfm maintenance-point local mep
---------------------------------------------------------------------------
---------------------------------------------------------------------------
1 Oper1 0 - MEP Gi0/3 Disabled

ECFM
maOper1 - Down 00:01:02:03:04:03 Active

2 Oper2 1 - MEP Gi0/3 Disabled
1 Oper3 2 1 MEP Gi0/3 Disabled
• Display the MEPs configured on the bridge.

% snmp0 walk table fsMIEcfmMepMacAddress {puts $table}
{1.3.6.1.4.1.2076.160.1.0.7.1.9.0.1.1.1 {OCTET STRING} 00:01:02:03:04:03}
{1.3.6.1.4.1.2076.160.1.0.7.1.9.0.2.1.2 {OCTET STRING} 00:01:02:03:04:03}
{1.3.6.1.4.1.2076.160.1.0.7.1.9.0.3.1.1 {OCTET STRING} 00:01:02:03:04:03}
Maintenance end points are displayed either based on the interface, domain name or domain level, if one
of the inputs is selected; otherwise all the Maintenance points are displayed.
Chapter
4
4.Configuring ECFM in Multiple Instance Mode
MI Bridge-A MI Bridge-B
Switch 1 Switch 2 Switch 1 Switch 2
P1 P2 P1 P2
Down MEP
Figure 4-1: Configuration of ECFM with MI
Switch configuration mode is used for configuration per switch (virtual context)

Switch Configuration The Global iss(config-switch)# To exit to the Global
Configuration mode Configuration mode
command switch the exit command is
<context-name> is used and to exit to
used to enter the the Privileged EXEC
switch Configuration mode the end
mode. command is used.

ECFM
Refer Figure 4-1 for topology. Here Maintenance Points (MEP) are configured in a particular switch
(switch 1, switch 2) of the bridges (Bridge-A, Bridge-B) and Continuity check (CC), Linktrace and
Loopback protocols are used to check the connectivity between the two bridges. Frame Delay and Frame
Loss protocols are used for performance monitoring.
For Multiple Instance configuration, enable all the interfaces and map the interfaces to the corresponding
switch (virtual instance).
The commands for the configurations of ECFM are common for both single and multiple instances. Refer
3.1 for the list of commands and interface type.
4.1 Creating Virtual Context
This section describes the creation and configuration of virtual contexts in the bridges (Bridge-A and
Bridge-B).
At Bridge-A and Bridge-B

• Enter the global configuration mode, create virtual contexts and set the bridge mode and spanning
tree mode for the created contexts.
iss(config)# switch 1
iss(config-switch)# bridge-mode customer
iss(config-switch)# spanning-tree mode mst
iss(config-switch)# end
• Enable interfaces and map them to a particular switch.
iss(config-if)# no shutdown
iss(config-if)# map switch 1
CHAPTER 4: CONFIGURING ECFM IN MULTIPLE INSTANCE MODE

• Set bridge mode and spanning tree mode.
[Index: ContextID = 1]
% snmp0 set {{fsVCStatus.1 createAndGo}}
% snmp0 set {{fsMIVlanBridgeMode.1 customerBridge}}
% snmp0 set {{fsMIMstSystemControl.1 start}}
% snmp0 set {{fsMIMstModuleStatus.1 enabled}}
• Enable interfaces and map them to a particular switch.

% snmp0 set {{ifMainRowStatus.1 createAndWait}}
% snmp0 set {{ifAlias.1 Slot0/1}}
% snmp0 set {{ifMainType.1 ethernetCsmacd}}
% snmp0 set {{ifMainRowStatus.1 active}}
% snmp0 set {{fsVcIfRowStatus.1 createAndWait}}


ECFM


4.2 Creating VLAN
This section describes the creation of VLANs in the bridges (Bridge-A and Bridge-B), and the mapping of
the interfaces to the created VLAN.

• Create VLAN and make interfaces as member port of this VLAN.
iss(config-switch)# vlan 2
iss(config-switch-vlan)# ports gigabitethernet 0/1,0/2
iss(config-switch-vlan)# vlan active
iss(config-switch-vlan)# end

• Create VLAN and make interfaces as member port of this VLAN.
[Index: ContextID = 1, Vlan-ID = 2]
[Index: ContextID = 1, Vlan-ID = 2, Interface Number = 1]



4.3 Initializing ECFM
This section describes the enabling of ECFM and traceroute caching at both the bridges (Bridge-A and
Bridge-B).

• Initialize ECFM.
iss(config-switch)# ethernet cfm start
iss(config-switch)# ethernet cfm enable
• Enable Traceroute caching.
iss(config-switch)# ethernet cfm traceroute cache
iss(config-switch)# exit

• Initialize ECFM. [Index: ContextID = 1]
% snmp0 set {{fsMIEcfmSystemControl.1 start}}
• Enable Traceroute caching. [Index: ContextID = 1]

% snmp0 set {{fsMIEcfmLtrCacheStatus.1 enabled}}
4.4 Configuring Maintenance Domain, Service and MEPs
This section describes the configuration of MD, MA and MEPs at bridges.

ECFM

• Configure MD, Service and MEP List.
iss(config-switch)# ethernet cfm domain name OP1 level 5
iss(config-ether-ecfm)# service name maop1 vlan 2
iss(config-ether-ecfm)# mep crosscheck mpid 10 vlan 2
iss(config-ether-ecfm)# end
At Bridge-A
• Configure the Down MEP.
At Bridge-B
iss(config-either-mep)# end

• Configure MD, Service and MEP List.
% snmp0 set {{fsMIEcfmMdFormat.1.1 charString}}
% snmp0 set {{fsMIEcfmMdName.1.1 4F:50:31}}

% snmp0 set {{fsMIEcfmMaFormat.1.1.1 charString}}
% snmp0 set {{fsMIEcfmMaName.1.1.1 6D:61:6F:70:31}}
% snmp0 set {{fsMIEcfmMaCcmInterval.1.1.1 interval1s}}
[Index: ContextID = 1, MD-Index = 1, MA-Index = 1, MEP-ID = 10]

% snmp0 set {{fsMIEcfmMaMepListRowStatus.1.1.1.10 createAndGo}}

At Bridge-A
• Configure the Down MEP. [Index: ContextID = 1, MD-Index = 1, MA-Index = 1, MEP-ID = 10]
% snmp0 set {{fsMIEcfmMepDirection.1.1.1.10 down}}
At Bridge-B
4.5 Detecting Fault
This section describes the enabling of the CCM transmission for fault detection.

ECFM

• Enable CCM transmission
iss(config-switch)# ethernet cfm cc enable level 5 vlan 2


4.6 Verifying and Isolating Fault
This section describes the verification and isolation of fault at bridge (Bridge-A).
At Bridge-A
• Initiate the LBM from an MEP on virtual switch 1 of bridge Bridge-A.
iss# ping ethernet mac 00:02:02:03:04:02 domain OP1 vlan 2 switch 1

• Initiate Traceroute from an MEP on virtual switch 1 of bridge Bridge-A.

iss# traceroute ethernet mac 00:02:02:03:04:02 domain OP1 vlan 2 switch 1
Traceroute to Macaddress 00:02:02:03:04:02 in domain OP1 at level 5
with vlanId 2
with vlanId 2
------------------------------------------------------------------------
------------------------------------------------------------------------
1 00:01:02:03:04:01:00:02 00:02:02:03:04:02 IngBlocked RlyHit
00:02:02:03:04:01:00:02 - - Terminal MEP
At Bridge-A
• Initiate the LBM from an MEP on virtual switch 1 of bridge Bridge-A. [Index: ContextID = 1, MD-Index
= 1, MA-Index = 1, MEP-ID = 10]
% snmp0 set {{fsMIEcfmMepTransmitLbmMessages.1.1.1.10 5}}
% snmp0 set {{fsMIEcfmMepTransmitLbmDestMacAddress.1.1.1.10 00:02:02:03:04:02}}
% snmp0 set {{fsMIEcfmMepTransmitLbmDestIsMepId.1.1.1.10 false}}
% snmp0 set {{fsMIEcfmMepTransmitLbmStatus.1.1.1.10 transmit}}
Get the value of following object to check whether LBM is transmitted successfully
% snmp0 get {fsMIEcfmMepLbrIn.1.1.1.10}
{1.3.6.1.4.1.2076.160.1.0.7.1.20.1.1.1.10 Unsigned32 5}
• Initiate Traceroute from an MEP on virtual switch 1 of bridge Bridge-A. [Index: ContextID = 1, MD-
Index = 1, MA-Index = 1, MEP-ID = 10]
% snmp0 set {{fsMIEcfmMepTransmitLtmTargetMacAddress.1.1.1.10 00:02:02:03:04:02}}
Check whether LTM is transmitted successfully and LTR is received.

% snmp0 walk x fsMIEcfmLtrTable { puts $x }
{1.3.6.1.4.1.2076.160.1.0.8.1.3.1.1.1.10.1.1 Unsigned32 63}
{1.3.6.1.4.1.2076.160.1.0.8.1.4.1.1.1.10.1.1 INTEGER false}
{1.3.6.1.4.1.2076.160.1.0.8.1.5.1.1.1.10.1.1 INTEGER true}

ECFM
{1.3.6.1.4.1.2076.160.1.0.8.1.6.1.1.1.10.1.1 {OCTET STRING}

00:01:02:03:04:02:00:02}
{1.3.6.1.4.1.2076.160.1.0.8.1.7.1.1.1.10.1.1 {OCTET STRING}
00:02:02:03:04:01:00:02}
{1.3.6.1.4.1.2076.160.1.0.8.1.8.1.1.1.10.1.1 INTEGER rlyHit}
{1.3.6.1.4.1.2076.160.1.0.8.1.9.1.1.1.10.1.1 INTEGER 0}
{1.3.6.1.4.1.2076.160.1.0.8.1.10.1.1.1.10.1.1 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.12.1.1.1.10.1.1 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.13.1.1.1.10.1.1 INTEGER ingDown}
{1.3.6.1.4.1.2076.160.1.0.8.1.14.1.1.1.10.1.1 {OCTET STRING}
00:02:02:03:04:02}
{1.3.6.1.4.1.2076.160.1.0.8.1.15.1.1.1.10.1.1 INTEGER 1}
{1.3.6.1.4.1.2076.160.1.0.8.1.16.1.1.1.10.1.1 {OCTET STRING}
53:6C:6F:74:30:2F:32}
{1.3.6.1.4.1.2076.160.1.0.8.1.17.1.1.1.10.1.1 INTEGER 0}
{1.3.6.1.4.1.2076.160.1.0.8.1.18.1.1.1.10.1.1 {OCTET STRING}
00:00:00:00:00:00}
{1.3.6.1.4.1.2076.160.1.0.8.1.19.1.1.1.10.1.1 INTEGER 0}
{1.3.6.1.4.1.2076.160.1.0.8.1.20.1.1.1.10.1.1 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.21.1.1.1.10.1.1 {OCTET STRING}
1F:00:04:00:02}
4.7 Initializing Y.1731
This section describes the enabling of Y.1731 on virtual switch 1 of the bridges (Bridge-A and Bridge-B),
for Y.1731 compliant features.

• Enable Y.1731 on virtual switch 1.
iss(config-switch)# ethernet cfm y1731 enable

• Enable Y.1731 on virtual switch 1. [Index: ContextID = 1]
4.8 Measuring Frame Loss
The section describes the initiation of frame loss measurement at bridge (Bridge-A).
At Bridge-A
• Initiate single-ended frame loss from an MEP on virtual switch 1 of bridge Bridge-A.
iss# ethernet cfm frame loss level 5 vlan 2 mac 00:02:02:03:04:02 count 5 switch 1
iss# show ethernet cfm frame loss buffer detail switch 1
Switch 1
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:02:02:03:04:02 0 0 70ms
00:02:02:03:04:02 1 2 70ms
00:02:02:03:04:02 1 1 70ms
00:02:02:03:04:02 1 1 70ms
00:02:02:03:04:02 1 1 70ms
--- 00:01:02:03:04:02 single-ended frame loss statistics ---

timestamp = 25 Aug 2008 15:36:4, packets sent = 5, packets received = 5,
near-end loss max/avg/min = 1/0/0,
far-end loss max/avg/min = 2/1/0

ECFM
At Bridge-A
• Initiate single-ended frame loss from an MEP on virtual switch 1 of bridge Bridge-A. [Index: ContextID
= 1, MD-Index = 1, MA-Index = 1, MEP-ID = 10]
% snmp0 set {{fsMIY1731MepTransmitLmmInterval.1.1.1.10 interval1s}}
% snmp0 set {{fsMIY1731MepTransmitLmmDestMacAddress.1.1.1.10 00:02:02:03:04:02}}
• Verify whether the MAC address, interface index, time stamp and measurement time fileds are
updated in the frame loss rolling buffer.
[Index: ContextID = 1, MD-Index = 1, MA-Index = 1, MEP-ID = 10, TransID = 1, Seq No = 2]
% snmp0 get {fsMIY1731FlPeerMepMacAddress.1.1.1.10.1.2}
{1.3.6.1.4.1.29601.2.7.1.2.12.1.4.1.1.1.10.1.2 {OCTET STRING}
00:02:02:03:04:02}
% snmp0 get {fsMIY1731FlIfIndex.1.1.1.10.1.2}
{1.3.6.1.4.1.29601.2.7.1.2.12.1.5.1.1.1.10.1.2 INTEGER 2}
% snmp0 get {fsMIY1731FlMeasurementTimeStamp.1.1.1.10.1.2}
{1.3.6.1.4.1.29601.2.7.1.2.12.1.3.1.1.1.10.1.2 TimeTicks {0d 0:00:30.14}}
% snmp0 get {fsMIY1731FlMeasurementTime.1.1.1.10.1.2}
{1.3.6.1.4.1.29601.2.7.1.2.12.1.8.1.1.1.10.1.2 INTEGER 70}
4.9 Measuring Frame Delay
This section describes the initiation of frame delay measurement at bridge (Bridge-A).
At Bridge-A
• Initiate two-way frame delay from an MEP on virtual switch 1 of bridge Bridge-A.
iss# ethernet cfm frame delay start type two-way level 5 vlan 2 mac 00:02:02:03:04:02 count 5
switch 1
iss# show ethernet cfm frame delay buffer detail switch 1
Switch 1
MEP-ID : 10
Level : 5
VLAN-ID : 2
peer mac-address frame-delay IFDV FDV

----------------- ----------- ---- ---
00:02:02:03:04:02 50.00ms 0.000ms 0.000ms
00:02:02:03:04:02 60.00ms 10.00ms 10.00ms
00:02:02:03:04:02 60.00ms 10.00ms 0.000ms
00:02:02:03:04:02 60.00ms 10.00ms 0.000ms
00:02:02:03:04:02 70.00ms 20.00ms 10.00ms
--- 00:01:02:03:04:02 two-way frame delay statistics ---

delay min/avg/max = 50.00ms/60.00ms/70.00ms,
variation avg IFDV/FDV = 10.00ms/4.000ms
At Bridge-A
• Initiate two-way frame delay from an MEP on virtual switch 1 of bridge Bridge-A. [Index: ContextID =
1, MD-Index = 1, MA-Index = 1, MEP-ID = 10]
% snmp0 set {{fsMIY1731MepTransmitDmInterval.1.1.1.10 100}}
% snmp0 set {{fsMIY1731MepTransmitDmDestMacAddress.1.1.1.10 00:02:02:03:04:02}}
• View the number for DMM PDUs transmitted. [Index: Interface Number = 2]
% snmp0 get {fsMIY1731PortDmmOut.2}
{1.3.6.1.4.1.29601.2.7.1.1.1.1.14.2 Unsigned32 5}
4.10 Initiating Test Message
This section describes the initiation of test messages at bridge (Bridge-A).

ECFM
At Bridge-A
• Initiate test messages from an MEP on virtual switch 1 of bridge Bridge-A.
iss# ethernet cfm test mac 00:02:02:03:04:02 level 5 vlan 2 count 5 switch 1
60 bytes to 00:02:02:03:04:02: seq_no=0
60 bytes to 00:02:02:03:04:02: seq_no=1
60 bytes to 00:02:02:03:04:02: seq_no=2
60 bytes to 00:02:02:03:04:02: seq_no=3
60 bytes to 00:02:02:03:04:02: seq_no=4
--- 00:02:02:03:04:02 test statistics ---
At Bridge-A
• Initiate test messages from an MEP on virtual switch 1 of bridge Bridge-A. [Index: ContextID = 1, MD-
% snmp0 set {{fsMIY1731MepTransmitTstDestType.1.1.1.10 multicast}}
% snmp0 set {{fsMIY1731MepTransmitTstDestMepId.1.1.1.10 30}}
% snmp0 set {{fsMIY1731MepTransmitTstStatus.1.1.1.10 start}}
• Verify whether the test message counter is incremented for TEST messages sent. [Index: ContextID =
1, MD-Index = 1, MA-Index = 1, MEP-ID = 10]
% snmp0 get {fsMIY1731MepTstOut.1.1.1.10}
{1.3.6.1.4.1.29601.2.7.1.2.4.1.58.1.1.1.10 Unsigned32 4}
4.11 Creating Test MD
This section describes the creation of an MD on switch 2.
At Bridge-A
• Configure MD on switch 2.
iss(config-switch)# ethernet cfm domain name MD2 level 2

• View the output on Bridge-A for virtual switch 1.

iss# show ethernet cfm domain switch 1
Switch 1
Domain Name : OP1
Index : 1
Level : 5
Vlan Priority : 7
Drop Eligibility : Disabled
MHF Creation Criteria : none
Sender Id Permission : none
Total Services : 1
Vlan Crosscheck ServiceID

2 Enabled maop1
Crosscheck:
MPID Vlan Type Mep-Up
10 2 Local Yes
30 2 Remote Yes
• View the ECFM MD configuration information at all the switches (Switch 1, Switch2 of Bridge-A),
iss# show ethernet cfm domain
Switch default
Switch 1
Domain Name : OP1

Index : 1
Level : 5
Vlan Priority : 7
Total Services : 1

ECFM
Vlan Crosscheck ServiceID

2 Enabled maop1
Crosscheck:
10 2 Local Yes
30 2 Remote Yes
Switch 2
Domain Name : MD2

Index : 1
Level : 2
Vlan Priority : 7
Total Services : 0
Crosscheck:
At Bridge-A
• Configure MD on switch 2. [Index: ContextID = 2, MD-Index = 1]
• View the information on Bridge-A for virtual switch 1. [Index: ContextID = 1, MD-Index = 1]
% snmp0 get {fsMIEcfmMdFormat.1.1}
% snmp0 get {fsMIEcfmMdName.1.1}
{1.3.6.1.4.1.2076.160.1.0.4.1.3.1.1 {OCTET STRING} 4F:50:31}
% snmp0 get {fsMIEcfmMdMdLevel.1.1}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.1.1 INTEGER 5}

% snmp0 get {fsMIEcfmMaFormat.1.1.1}
% snmp0 get {fsMIEcfmMaName.1.1.1}
{1.3.6.1.4.1.2076.160.1.0.5.1.4.1.1.1 {OCTET STRING} 6D:61:6F:70:31}
% snmp0 get {fsMIEcfmMaCcmInterval.1.1.1}
% snmp0 get {fsMIEcfmMaPrimaryVlanId.1.1.1}
{1.3.6.1.4.1.2076.160.1.0.5.1.2.1.1.1 INTEGER 2}

% snmp0 get {fsMIEcfmMepPrimaryVid.1.1.1.10}
{1.3.6.1.4.1.2076.160.1.0.7.1.4.1.1.1.10 Unsigned32 0}
% snmp0 get {fsMIEcfmMepIfIndex.1.1.1.10}
{1.3.6.1.4.1.2076.160.1.0.7.1.2.1.1.1.10 INTEGER 2}
% snmp0 get {fsMIEcfmMepDirection.1.1.1.10}
{1.3.6.1.4.1.2076.160.1.0.7.1.3.1.1.1.10 INTEGER down}
% snmp0 get {fsMIEcfmMepActive.1.1.1.10}
{1.3.6.1.4.1.2076.160.1.0.7.1.5.1.1.1.10 INTEGER true}
• View the information on Bridge-A for virtual switch 2.

{1.3.6.1.4.1.2076.160.1.0.4.1.3.2.1 {OCTET STRING} 4F:50:32}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.2.1 INTEGER 2}

Chapter
5
5.Flow Based Configuration
5.1 Configuring ECFM on Customer Bridges

The following section describes the configuration of the ECFM functionality on the following sample
topology (Refer Figure 4-1 for topology).

ECFM
A B
P1 P1
CUST1 P2 P2 CUST2
Bridge Bridge
(OP1) (OP2)
P3 P3
P2
CUST3
P3 Bridge
(OP3)
Entity
P1 Up MEP
MIP
C
Down MEP
Figure 5-1: Configuration of ECFM on Customer Bridges

MAC Address of ports on the bridges are of form 00:0m:02:03:04:0n, where m is bridge number and n is
the port number for that bridge in this sample topology.
Figure 5-1 depicts that Maintenance Points (MIP, MEP) are configured on various bridges at same MD
Level and VLAN MEPs are configured on CUST1 and CUST3 and an MIP is configured on CUST2.
Connectivity is checked between CUST1 CUST2, and CUST3 through Continuity Check Protocol. A Link
failure is intentionally incorporated at P2 of CUST3. Loopback and Linktrace protocols are then used for
isolation and verification of the same. Frame Delay and Frame Loss protocols are used for performance
monitoring.
5.1.1 Creating Interfaces
This section describes the creation and configuration of interfaces at CUST1, CUST2 and CUST3.
CHAPTER 5: FLOW BASED CONFIGURATION
At CUST1, CUST2 and CUST3

• Enable interfaces

• Enable interfaces


5.1.2 Creating VLAN
This section describes the creation of VLAN on bridges (CUST1, CUST2 and CUST3) and assigning of
member ports for the created VLAN.

ECFM

• Create VLAN and assign member ports for this VLAN
iss(config)# vlan 2
iss(config-vlan)# exit

• Create VLAN and assign member ports for this VLAN
5.1.3 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).

• Enable ECFM
iss(config) # ethernet cfm enable
• Enable Traceroute caching
iss(config) # ethernet cfm traceroute cache
• Enable MIP CCM database
iss(config) # ethernet cfm mip ccm-database

• Enable ECFM. [Index: ContextID = 0]
• Enable Traceroute caching. [Index: ContextID = 0]
• Enable MIP CCM database. [Index: ContextID = 0]
% snmp0 set {{fsMIEcfmMipCcmDbStatus.0 enabled}}
5.1.4 Configuring Maintenance Domain, Service and MEPs
This section describes the configuration of MD, MA and MEPs on bridges.
At CUST1 and CUST3

• Configure MD, Service and MEP list
iss(config) # ethernet cfm domain name OP1 level 5
iss(config-ether-ecfm) # service name maop1 vlan 2
At CUST1
At CUST3

ECFM
At CUST1 and CUST3

• Create the MD. [Index: ContextID = 0, MD-Index = 1]
• Create the MA. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1]

• Configure the MEP List.


At CUST1
At CUST3
5.1.5 Enabling CCM transmission
This section describes the enabling of the CCM transmission on bridges CUST1 and CUST3
At CUST1 and CUST3

iss(config)# exit
At CUST1
• Enable CCM transmission. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-ID = 10]
% snmp0 set {{fsMIEcfmExtMepCciEnabled.0.1.1.10 true}}
At CUST3
• Enable CCM transmission. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-ID = 30]

ECFM
5.1.6 Configuring MIP
This section describes the configuration of Default Domain with VLAN and MdLevel for MIP creation, and
configuration of MIP in the default domain on the bridge CUST2.
At CUST2
• Configure default domain and MIP
iss(config) # ethernet cfm default-domain vlan 2 level 5 mip-creation-criteria default
iss(config-if)# ethernet cfm mip level 5 vlan 2 active
At CUST2
• Configure default domain and MIP
[Index: Interface Number = 2, MD-level=5, Vlan = 2]

% snmp0 set {{fsMIEcfmMipRowStatus.2.5.2 createAndWait}}
5.1.7 Verifying Configured MPs (MEP and MIP)
This section describes the verification of the configured MEP and MIP on the bridges.
At CUST1
• Display the details of all the MEPs and MIPs.
---------------------------------------------------------------------------
---------------------------------------------------------------------------
10 OP1 5 2 MEP Gi0/2 Enabled

maop1 - Down 00:01:02:03:04:02 Active
At CUST2
---------------------------------------------------------------------------
---------------------------------------------------------------------------
- - 5 2 MIP Gi0/2 -
- - - 00:02:02:03:04:02 Active
At CUST3
---------------------------------------------------------------------------
---------------------------------------------------------------------------
maop1 - Down 00:03:02:03:04:02 Active
At CUST1
{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.1 {OCTET STRING} 4F:50:31}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.1 INTEGER 5}


ECFM

{1.3.6.1.4.1.2076.160.1.0.5.1.4.0.1.1 {OCTET STRING} 6D:61:6F:70:31}
{1.3.6.1.4.1.2076.160.1.0.5.1.2.0.1.1 INTEGER 2}

{1.3.6.1.4.1.2076.160.1.0.7.1.4.0.1.1.10 Unsigned32 0}
{1.3.6.1.4.1.2076.160.1.0.7.1.2.0.1.1.10 INTEGER 2}
{1.3.6.1.4.1.2076.160.1.0.7.1.3.0.1.1.10 INTEGER down}
{1.3.6.1.4.1.2076.160.1.0.7.1.5.0.1.1.10 INTEGER true}
At CUST2
% snmp0 get {fsMIEcfmDefaultMdDefMhfCreation.0}
{1.3.6.1.4.1.2076.160.1.0.1.1.5.0 INTEGER defMHFdefault}
% snmp0 get {fsMIEcfmDefaultMdDefLevel.0}
{1.3.6.1.4.1.2076.160.1.0.1.1.4.0 INTEGER 5}
[Index: Interface Number = 2, MD-level=5, Vlan = 2]

% snmp0 get {fsMIEcfmMipRowStatus.2.5.2}
{1.3.6.1.4.1.2076.160.1.1.6.1.5.2.5.2 INTEGER active}
At CUST3
{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.1 {OCTET STRING} 4F:50:31}

{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.1 INTEGER 5}

{1.3.6.1.4.1.2076.160.1.0.5.1.4.0.1.1 {OCTET STRING} 6D:61:6F:70:31}
{1.3.6.1.4.1.2076.160.1.0.5.1.2.0.1.1 INTEGER 2}

{1.3.6.1.4.1.2076.160.1.0.7.1.4.0.1.1.30 Unsigned32 0}
{1.3.6.1.4.1.2076.160.1.0.7.1.2.0.1.1.30 INTEGER 2}
{1.3.6.1.4.1.2076.160.1.0.7.1.3.0.1.1.30 INTEGER down}
{1.3.6.1.4.1.2076.160.1.0.7.1.5.0.1.1.30 INTEGER true}
• Wait for 5 seconds to check for any link failure (error/fault/defect)
5.1.8 Checking for CCM Errors
This section describes the checking of CCM errors on the bridges (CUST1 and CUST3)
At CUST1
• Display the logged CFM continuity check error conditions
iss# show ethernet cfm errors
MEP-ID : 10
Level VLAN RMEP-ID Current defect type
----- ---- ------- -------------------
5 2 30 mac status defect
Implies that CUST-3 is sending CCM with port-status as blocked.

ECFM
At CUST3
MEP-ID : 30
----- ---- ------- -------------------
5 2 10 remote defect indication
Implies that CUST-1 is sending CCM with RDI as enabled.
At CUST1
• Display the logged CFM continuity check error conditions. [Index: ContextID = 0, MD-Index = 1, MA-
% snmp0 get {fsMIEcfmMepDefects.0.1.1.10}
{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.1.1.10 {OCTET STRING} 40}
At CUST3
{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.1.1.30 {OCTET STRING} 80}
5.1.9 Checking for Configured Remote Entities in the Network
This section describes the checking of configured MAs.
At CUST1
• Display information about all the configured CFM MAs
iss# 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 - Local Yes 00: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
iss# 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

ECFM
30 2 - Local Yes 00:03:02:03:04:02
At CUST1
• Display information about all the configured CFM MAs. [Index: ContextID = 0, MD-Index = 1, MA-
Index = 1, MEP-ID = 10, RemoteMEP-ID =30]
% snmp0 get {fsMIEcfmRMepMacAddress.0.1.1.10.30}
{1.3.6.1.4.1.2076.160.1.0.11.1.6.0.1.1.10.30 {OCTET STRING}
00:03:02:03:04:02}
At CUST3
• Display information about all the configured CFM MAs. [Index: ContextID = 0, MD-Index = 1, MA-
Index = 1, MEP-ID = 30, RemoteMEP-ID = 10]
% snmp0 get {fsMIEcfmRMepMacAddress.0.1.1.30.10}
{1.3.6.1.4.1.2076.160.1.0.11.1.6.0.1.1.30.10 {OCTET STRING}
00:01:02:03:04:02}
5.1.10 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.
At CUST3
• Make interface P2 down.
iss(config-if)# shutdown
• 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
Shows no error, as MIP cannot detect any link failure (error/fault/defect).
At CUST3
MEP-ID : 30
----- ---- ------- -------------------
At CUST3
• Make interface P2 as down. [Index: Interface Number = 2]
% snmp0 set {{ifMainAdminStatus.2 down}}
• Wait for 5 seconds and verify any link failure (error/fault/defect)
At CUST1
% snmp0 get {fsMIEcfmExtMepDefects.0.1.1.10}
{1.3.6.1.4.1.29601.2.13.1.2.3.1.14.0.1.1.10 {OCTET STRING} 20}
At CUST3
{1.3.6.1.4.1.29601.2.13.1.2.3.1.14.0.1.1.30 {OCTET STRING} 20}
5.1.11 Verifying and Isolating Fault
This section describes the verification and isolation of fault using loopback and link trace messages.

ECFM
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
iss# ping ethernet mac 00:03:02:03:04:02 domain OP1 vlan 2

iss#
• Initiate Traceroute to MEP at bridge CUST3 to isolate link failure (error/fault/defect).

iss# traceroute ethernet mac 00:03:02:03:04:02 domain OP1 vlan 2

with vlanId 2
---------------------------------------------------------------------------
---------------------------------------------------------------------------
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.

Shows no link failure between CUST1 and CUST2

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. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1,
MEP-ID = 10]
• Check whether the LBRs are not received.

{1.3.6.1.4.1.2076.160.1.0.7.1.20.0.1.1.10 Unsigned32 0}
• Initiate traceroute to MEP at bridge CUST1 for isolating link failure (error/fault/defect). [Index:
ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-ID = 10]
• Check whether LTM is transmitted successfully

{1.3.6.1.4.1.2076.160.1.0.8.1.3.0.1.1.10.2.1 Unsigned32 63}
{1.3.6.1.4.1.2076.160.1.0.8.1.4.0.1.1.10.2.1 INTEGER true}
{1.3.6.1.4.1.2076.160.1.0.8.1.5.0.1.1.10.2.1 INTEGER false}
{1.3.6.1.4.1.2076.160.1.0.8.1.6.0.1.1.10.2.1 {OCTET STRING}
00:01:02:03:04:01:00:02}
{1.3.6.1.4.1.2076.160.1.0.8.1.7.0.1.1.10.2.1 {OCTET STRING}
00:02:02:03:04:01:00:02}
{1.3.6.1.4.1.2076.160.1.0.8.1.8.0.1.1.10.2.1 INTEGER rlyFdb}
{1.3.6.1.4.1.2076.160.1.0.8.1.9.0.1.1.10.2.1 INTEGER 0}
{1.3.6.1.4.1.2076.160.1.0.8.1.10.0.1.1.10.2.1 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.12.0.1.1.10.2.1 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.13.0.1.1.10.2.1 INTEGER ingOk}
{1.3.6.1.4.1.2076.160.1.0.8.1.14.0.1.1.10.2.1 {OCTET STRING}
00:02:02:03:04:02}
{1.3.6.1.4.1.2076.160.1.0.8.1.15.0.1.1.10.2.1 INTEGER 1}

ECFM
{1.3.6.1.4.1.2076.160.1.0.8.1.16.0.1.1.10.2.1 {OCTET STRING}

53:6C:6F:74:30:2F:32}
{1.3.6.1.4.1.2076.160.1.0.8.1.17.0.1.1.10.2.1 INTEGER egrOK}
{1.3.6.1.4.1.2076.160.1.0.8.1.18.0.1.1.10.2.1 {OCTET STRING}
00:02:02:03:04:03}
{1.3.6.1.4.1.2076.160.1.0.8.1.19.0.1.1.10.2.1 INTEGER 1}
{1.3.6.1.4.1.2076.160.1.0.8.1.20.0.1.1.10.2.1 {OCTET STRING}
53:6C:6F:74:30:2F:33}
{1.3.6.1.4.1.2076.160.1.0.8.1.21.0.1.1.10.2.1 {OCTET STRING}
1F:00:04:00:02}
• Initiate the loopback transaction to MIP at CUST2 for verifying if there is a link failure. [Index:
• Check whether LBMs are transmitted successfully and LBRs are received

{1.3.6.1.4.1.2076.160.1.0.7.1.20.0.1.1.10 Unsigned32 5}
Shows no link failure between CUST1 and CUST2
5.1.12 Bridge Up Interface
This section describes the configuration of interface.
At CUST3
• Make interface P2 of CUST3 as up.
• Wait for 5 seconds and check error/fault/defect.

At CUST3
• Set interface P2 of CUST3 as up. [Index: Interface Number = 2]

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

ECFM
At CUST1
• Wait for 5 seconds after configuring the interface as up and then check for error/fault/defect. [Index:
{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.1.1.10 {OCTET STRING} 40}
At CUST3
• Wait for 5 seconds after configuring the interface as up and then check for error/fault/defect. [Index:
{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.1.1.30 {OCTET STRING} 80}
This section describes the initiation of the loop back and link trace messages to verify and isolate fault.
At CUST1
• Initiate the Loopback transaction from MEP at CUST1 to MEP at CUST3.

• Initiate Traceroute from MEP at CUST1 to MEP at CUST3

with vlanId 2
---------------------------------------------------------------------------


---------------------------------------------------------------------------
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
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
At CUST1
• Initiate the loopback transaction from MEP at CUST1 to MEP at CUST3. [Index: ContextID = 0, MD-
• Check whether the LBRs are not received.

{1.3.6.1.4.1.2076.160.1.0.7.1.20.0.1.1.10 Unsigned32 10}
• Initiate traceroute from MEP at CUST1 to MEP at CUST3. [Index: ContextID = 0, MD-Index = 1, MA-
• Check whether LTM is transmitted successfully

{1.3.6.1.4.1.2076.160.1.0.8.1.3.0.1.1.10.3.1 Unsigned32 63}
{1.3.6.1.4.1.2076.160.1.0.8.1.3.0.1.1.10.3.2 Unsigned32 62}
{1.3.6.1.4.1.2076.160.1.0.8.1.4.0.1.1.10.3.1 INTEGER true}
{1.3.6.1.4.1.2076.160.1.0.8.1.4.0.1.1.10.3.2 INTEGER false}
{1.3.6.1.4.1.2076.160.1.0.8.1.5.0.1.1.10.3.1 INTEGER false}
{1.3.6.1.4.1.2076.160.1.0.8.1.5.0.1.1.10.3.2 INTEGER true}
{1.3.6.1.4.1.2076.160.1.0.8.1.6.0.1.1.10.3.1 {OCTET STRING}
00:01:02:03:04:01:00:02}

ECFM
{1.3.6.1.4.1.2076.160.1.0.8.1.6.0.1.1.10.3.2 {OCTET STRING}

00:02:02:03:04:01:00:02}
{1.3.6.1.4.1.2076.160.1.0.8.1.7.0.1.1.10.3.1 {OCTET STRING}
00:02:02:03:04:01:00:02}
{1.3.6.1.4.1.2076.160.1.0.8.1.7.0.1.1.10.3.2 {OCTET STRING}
00:03:02:03:04:01:00:02}
{1.3.6.1.4.1.2076.160.1.0.8.1.8.0.1.1.10.3.1 INTEGER rlyFdb}
{1.3.6.1.4.1.2076.160.1.0.8.1.8.0.1.1.10.3.2 INTEGER rlyHit}
{1.3.6.1.4.1.2076.160.1.0.8.1.9.0.1.1.10.3.1 INTEGER 0}
{1.3.6.1.4.1.2076.160.1.0.8.1.9.0.1.1.10.3.2 INTEGER 0}
{1.3.6.1.4.1.2076.160.1.0.8.1.10.0.1.1.10.3.1 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.10.0.1.1.10.3.2 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.12.0.1.1.10.3.1 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.12.0.1.1.10.3.2 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.13.0.1.1.10.3.1 INTEGER ingOk}
{1.3.6.1.4.1.2076.160.1.0.8.1.13.0.1.1.10.3.2 INTEGER ingDown}
{1.3.6.1.4.1.2076.160.1.0.8.1.14.0.1.1.10.3.1 {OCTET STRING}
00:02:02:03:04:02}
{1.3.6.1.4.1.2076.160.1.0.8.1.14.0.1.1.10.3.2 {OCTET STRING}
00:03:02:03:04:02}
{1.3.6.1.4.1.2076.160.1.0.8.1.15.0.1.1.10.3.1 INTEGER 1}
{1.3.6.1.4.1.2076.160.1.0.8.1.15.0.1.1.10.3.2 INTEGER 1}
{1.3.6.1.4.1.2076.160.1.0.8.1.16.0.1.1.10.3.1 {OCTET STRING}
53:6C:6F:74:30:2F:32}
{1.3.6.1.4.1.2076.160.1.0.8.1.16.0.1.1.10.3.2 {OCTET STRING}
53:6C:6F:74:30:2F:32}
{1.3.6.1.4.1.2076.160.1.0.8.1.17.0.1.1.10.3.1 INTEGER egrOK}
{1.3.6.1.4.1.2076.160.1.0.8.1.17.0.1.1.10.3.2 INTEGER 0}
{1.3.6.1.4.1.2076.160.1.0.8.1.18.0.1.1.10.3.1 {OCTET STRING}
00:02:02:03:04:03}
{1.3.6.1.4.1.2076.160.1.0.8.1.18.0.1.1.10.3.2 {OCTET STRING}
00:00:00:00:00:00}
{1.3.6.1.4.1.2076.160.1.0.8.1.19.0.1.1.10.3.1 INTEGER 1}
{1.3.6.1.4.1.2076.160.1.0.8.1.19.0.1.1.10.3.2 INTEGER 0}
{1.3.6.1.4.1.2076.160.1.0.8.1.20.0.1.1.10.3.1 {OCTET STRING}
53:6C:6F:74:30:2F:33}
{1.3.6.1.4.1.2076.160.1.0.8.1.20.0.1.1.10.3.2 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.21.0.1.1.10.3.1 {OCTET STRING}
1F:00:04:00:02}

{1.3.6.1.4.1.2076.160.1.0.8.1.21.0.1.1.10.3.2 {OCTET STRING}

1F:00:04:00:03}
5.1.15 Enabling Y1731
This section describes the enabling of Y.1731.

• Enable Y.1731
iss(config) # ethernet cfm y1731 enable
iss(config) # exit

• Enable Y.1731. [Index: ContextID = 0]
5.1.16 Initiating Frame Delay Measurement
This section describes the intiation of frame delay measurement.
At CUST1
• Initiate Two-way Frame delay measurement from MEP at CUST1 to MEP at CUST3.
iss# 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.
iss# show ethernet cfm frame delay buffer detail

MEP-ID : 10
Level : 5
VLAN-ID : 2
peer mac-address frame-delay IFDV FDV

ECFM
----------------- ----------- ---- ---

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
--- 00:01:02:03:04:02 two-way frame delay statistics ---

delay min/avg/max = 110.0ms/118.0ms/120.0ms,
variation avg IFDV/FDV = 8.000ms/2.000ms
At CUST1
• Initiate two-way frame delay measurement from MEP at CUST1 to MEP at CUST3. [Index: ContextID
= 0, MD-Index = 1, MA-Index = 1, MEP-ID = 10]
• Verify whether the delay measurement message counter is incremented for delay measurement
messages sent
% snmp0 get {fsMIY1731PortDmmOut.2}
{1.3.6.1.4.1.29601.2.7.1.1.1.1.14.2 Unsigned32 5}
5.1.17 Initiating Frame Loss Measurement
This section describes the intiation of frame loss measurement.
At CUST1
• Initiate Frame loss measurement from MEP at CUST1 to MEP at CUST3.
iss# 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.
iss# show ethernet cfm frame loss buffer detail

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 ---

near-end loss max/avg/min = 1/0/0,
far-end loss max/avg/min = 1/0/0
At CUST1
• Initiate frame loss measurement from MEP at CUST1 to MEP at CUST3. [Index: ContextID = 0, MD-
• Verify whether the fields in the frame loss rolling buffer are updated. [Index: ContextID = 0, MD-Index
= 1, MA-Index = 1, MEP-ID = 10, TransID = 1, Seq No = 2]
% snmp0 get {fsMIY1731FlPeerMepMacAddress.0.1.1.10.1.2}
{1.3.6.1.4.1.29601.2.7.1.2.12.1.4.0.1.1.10.1.2 {OCTET STRING}
00:03:02:03:04:02}
% snmp0 get {fsMIY1731FlIfIndex.0.1.1.10.1.2}

ECFM
{1.3.6.1.4.1.29601.2.7.1.2.12.1.5.0.1.1.10.1.2 INTEGER 2}
% snmp0 get {fsMIY1731FlMeasurementTimeStamp.0.1.1.10.1.2}
{1.3.6.1.4.1.29601.2.7.1.2.12.1.3.0.1.1.10.1.2 TimeTicks {0d 0:00:30.14}}
% snmp0 get {fsMIY1731FlMeasurementTime.0.1.1.10.1.2}
{1.3.6.1.4.1.29601.2.7.1.2.12.1.8.0.1.1.10.1.2 INTEGER 70}
5.1.18 Initiating Test Message
This section describes the intiation of the test messages.
At CUST1
• Initiate Test message from MEP at CUST1 to MEP at CUST3.
iss# ethernet cfm test mac 00:03:02:03:04:02 domain OP1 vlan 2 count 5

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 ---
At CUST1
• Initiate test message from MEP at CUST1 to MEP at CUST3. [Index: ContextID = 0, MD-Index = 1,
MA-Index = 1, MEP-ID = 10]
• Verify whether the test counter in incremented for test messages sent. [Index: ContextID = 0, MD-
{1.3.6.1.4.1.29601.2.7.1.2.4.1.58.0.1.1.10 Unsigned32 4}

5.2 Configuring ECFM on Provider Bridges
The following sections describe the configuration of the ECFM functionality for provider bridges on the
following sample topology (Refer Figure 4-1 for topology)
Customer Network
(CB)
P4 Switch1 P3
P5 P2
Provider Network
Operator 1 Network P5 P2
(PEB)
Switch2
P4 P3
P2 P2
(PCB) (PCB)
Switch4 Switch3
P4 P4
P3 P3
P3 P3
(PCB) P4 P4 (PCB)
Switch8 Switch7
Bridge
P2 P2 CB Customer
PEB Provider Edge
P4 P3
PCB Provider Core
(PEB)
Switch6 Entity
Up MEP
Operator 2 Network P5 P2
MIP
Down MEP
P5 P2
Customer Network Color code

(CB)
P4 P3 Level 7 VLAN 2
Switch5
Level 7 VLAN 4
Level 4 VLAN 4
Level 2 VLAN 4
Figure 5-2: Configuration of ECFM on Provider bridges

ECFM
MAC Address of ports on the bridges are of form 00:0m:02:03:04:0n, where m is bridge number and n is
Figure 5-2 depicts a topology for a Provider bridged network consists of two customer bridges (Switch1,
Switch5), two provider edge bridges (Switch2, Switch6), and four provider core bridges (Switch3, Switch4,
Switch7, Switch8). Maintenance Points (MEP/MIP) are configured at same MD Level and VLAN shown by
the a color code, at same type of the bridges. For an example blue color represents MEPs are configured
at Level 7 and VLAN 2 at customer bridges (Switch1 and Switch5).
Connectivity is checked between all the bridges (Switch1 to Switch 8) through Continuity Check Protocol.
A Link failure is intentionally incorporated at P2 of Switch 5. Loopback and Linktrace protocols are then
used for verification and isolation respectively.AIS and LCK are used for fault suppression.
Connectivity at customer bridges is provided through two Provided Edge bridges and four Provider Core
bridges. Service is provided to Customer through the Provider Network and to Provider Network through
the Provider Core Network. Service is provided through configuration of CFM entities at respective MD
Level on customer and provider bridges.
5.2.1 Configuring the Bridge Mode
This section describes the configuration of bridge mode for the bridges.
At Switch1 and Switch5

• Set bridge-mode as customer and spanning tree mode as mst
iss#configure terminal
iss(config)# shutdown spanning-tree
iss(config)# set gvrp disable
iss(config)# set gmrp disable
iss(config)# shutdown garp
iss(config)# bridge-mode customer
iss(config)# no shutdown garp
iss(config)# set gvrp enable
iss(config)# spanning-tree mode mst

• Set bridge-mode as provider-edge and spanning tree mode as mst
iss(config)# bridge-mode provider-edge


At Switch3, Switch4, Switch7 and Switch8

• Set bridge-mode as provider-core and spanning tree mode as mst
iss(config)# bridge-mode provider-core

• Set bridge-mode as customerBridge. [Index: ContextID = 0]
% snmp0 set {{fsMIMstSystemControl.0 shutdown}}
% snmp0 set {{fsDot1qGvrpStatus.0 disabled}}
% snmp0 set {{fsDot1dGmrpStatus.0 disabled}}
% snmp0 set {{fsMIDot1qFutureGarpShutdownStatus.0 true}}
% snmp0 set {{fsMIEcfmSystemControl.0 shutdown}}
% snmp0 set {{fsMIDot1qFutureGarpShutdownStatus.0 false}}
% snmp0 set {{fsDot1qGvrpStatus.0 enabled}}
% snmp0 set {{fsDot1dGmrpStatus.0 enabled}}
% snmp0 set {{fsMIDot1qFutureVlanShutdownStatus.0 false}}

• Set bridge-mode as providerEdgeBridge. [Index: ContextID = 0]

ECFM

% snmp0 set {{fsMIVlanBridgeMode.0 providerEdgeBridge}}

• Set bridge-mode as providerCoreBridge. [Index: ContextID = 0]
% snmp0 set {{fsMIVlanBridgeMode.0 providerCoreBridge}}
5.2.2 Configuring Interfaces on Switches
This section describes the configuration of interfaces on the bridges.

• Create interfaces as up


At Switch3, Switch4, Swicth7 and Switch8



ECFM
At Switch3, Switch4, Swicth7 and Switch8

5.2.3 Configuring VLAN on Switches
This section describes the configuration of VLAN on switches.

• Create VLAN 2
iss(config)# vlan 2
• Make interfaces as member ports of this VLAN
iss(config-vlan)# ports gigabitethernet 0/2,0/5
• Set status of VLAN 2 as active

• Create VLAN 4 and make interfaces as member ports of this VLAN
iss(config)# vlan 4
iss(config-vlan)# ports gigabitethernet 0/2,0/3,0/4


• Create VLAN 2. [Index: ContextID = 0, Vlan-ID = 2]
• Make interfaces as member ports of this VLAN
• Set status of VLAN 2 as active. [Index: ContextID = 0, Vlan-ID = 2]

• Create VLAN 4 and make interfaces as member ports of this VLAN




5.2.4 Configuring Interface Types and VLAN Mapping
This section describes the configuration of interface types and mapping of VLAN.

ECFM
At Switch2
• Set interface as CustomerEdgePort
iss(config-if)# bridge port-type customerEdgePort
• Create VLAN and make interfaces as member ports of this VLAN and Port P2 as untagged member.
iss(config)# vlan 4
iss(config-vlan)# ports gigabitethernet 0/2,0/3,0/4,0/5 untagged gigabitethernet 0/2
• Configure CVID Registration table for interface with CVLAN to map with SVLAN
iss(config-if)# switchport dot1q customer vlan 2
iss(config-if)# switchport customer-vlan 2 service-vlan 4 untagged-pep false untagged-cep
false
• Configure interfaces type as providerNetworkPort
iss(config-if)# bridge port-type providerNetworkPort
At Switch6
• Configure interface type as customerNetworkPort port-based
iss(config-if)# bridge port-type customerNetworkPort port-based
• Creating VLAN and make interfaces as member ports of this VLAN and Port P2 as untagged member.
iss(config)# vlan 4
iss(config-vlan)# ports gigabitethernet 0/2,0/3,0/4,0/5 untagged gigabitethernet 0/2
• Set Primary Vlan (PVID) for an interface
iss(config-if)# switchport pvid 4

• Configure interface type as providerNetworkPort
At Switch2
• Set interface as customerEdgePort. [Index: Interface Number = 2]
% snmp0 set {{ifMainBrgPortType.2 customerEdgePort}}

% snmp0 set {{fsDot1qVlanStaticPort.0.4.2 addUntagged}}





ECFM
• Configure CVID Registration table for interface with CVLAN to map with SVLAN
% snmp0 set {{fsMIPbPortCVlan.2 2}}
[Index: Interface Number = 2, Vlan-ID =2]

% snmp0 set {{dot1adMICVidRegistrationRowStatus.2.2 createAndWait}}
% snmp0 set {{dot1adMICVidRegistrationSVid.2.2 4}}
% snmp0 set {{dot1adMICVidRegistrationUntaggedPep.2.2 false}}
% snmp0 set {{dot1adMICVidRegistrationUntaggedCep.2.2 false}}
% snmp0 set {{dot1adMICVidRegistrationRowStatus.2.2 active}}
• Configure interfaces type as providerNetworkPort

% snmp0 set {{ifMainBrgPortType.3 providerNetworkPort}}


At Switch6
• Configure interface type as customerNetworkPortPortBased. [Index: Interface Number = 2]
% snmp0 set {{ifMainBrgPortType.2 customerNetworkPortPortBased}}






• Set Primary VLAN (PVID) for an interface [Index: Interface Number = 2]

% snmp0 set {{fsDot1qPvid.2 4}}
• Configure interface type as providerNetworkPort



5.2.5 Initializing ECFM
This section describes the enabling of ECFM, MIP CCM database and traceroute caching.
At Switch1, Switch2, Switch3, Switch4, Switch5, Switch6, Switch7, Switch8

• Enable ECFM.
iss(config) # ethernet cfm enable
• Enable MIP CCM database
iss(config) # ethernet cfm mip ccm-database
• Enable Traceroute caching
iss(config) # ethernet cfm traceroute cache
At Switch1, Switch2, Switch3, Switch4, Switch5, Switch6, Switch7, Switch8

• Enable ECFM. [Index: ContextID = 0]

ECFM
• Enable MIP CCM database. [Index: ContextID = 0]

% snmp0 set {{fsMIEcfmMipCcmDbStatus.0 enabled}}
• Enable traceroute caching. [Index: ContextID = 0]
5.2.6 Configuring Maintenance Domain, Service and MEPs
This section describes the configuration of MD, MA and MEPs on the switches.
At Switch1
• Configure Maintenance Domain, Service and MEP List
iss(config)# ethernet cfm domain name OP7 level 7
iss(config- ether-ecfm)# exit
• Configure the Down Maintenance End Point (MEP)
• Enable the Continuity Check (CCM) transmission
• Enable the Traceroute Cache
At Switch5
• Configure the Down Maintenance End Point (MEP)


At Switch2
• Configure Maintenance Domain
• Configure Default Domain with VLAN and MdLevel for Maintenance Intermediate Point (MIP) creation
and configure MIP in the default domain.

• Configure the Up Maintenance End Point (MEP)

iss(config-ether-mep)# exit

iss(config)# ethernet cfm domain name OQ2 level 2
iss(config-ether-ecfm) # service name maop2 vlan 4 mip-creation-criteria default

ECFM


• Configure the Maintenane Intermediate Point (MIP)


At Switch6
and configure MIP in the default domain



• Configure Default Domain with VLAN and MdLevel for Maintenace Intermediate Point (MIP) creation


• Configure the Maintenance Intermediate Point (MIP)


At Switch3

ECFM




At Switch7





At Switch1
• Configure maintenance domain, service and MEP list.


ECFM




• Enable the CCM transmission. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-ID = 1]

• Enable the traceroute cache. [Index: ContextID = 0]

At Switch5






At Switch2
• Configure maintenance domain. [Index: ContextID = 0, MD-Index = 1]

ECFM
• Configure default domain with VLAN and MdLevel for MIP creation, and configure MIP in the default
domain.
[Index: Interface Number = 2, MD-level = 7, VlanID = 4]
• Configure maintenance domain, service and MEP list. [Index: ContextID = 0, MD-Index = 2]



• Configure the Up MEP. [Index: ContextID = 0, MD-Index = 2, MA-Index = 2, MEP-ID = 3]



• Configure default domain with VLAN and MdLevel for MIP creation. [Index: ContextID = 0]






ECFM

• Configure the MIP. [Index: Interface Number = 3, MD-level = 2, VlanID = 4]

• Enable the CCM transmission.


At Switch6
domain







• Configure default domain with VLAN and MdLevel for MIP creation. [Index: ContextID = 0]


ECFM






• Enable the CCM transmission




At Switch3
domain.

• Configure maintenance domain, service and MEP List



ECFM






At Switch7


domain. [Index: ContextID = 0]

• Configure maintenance domain, service and MEP List





ECFM

• Configure the MIP. [Index: ContextID = 0]



5.2.7 Verifying the configured MP (MEP, MIP)s
This section describes the verification of the configured MD, MA and MEPs.
At Switch1
---------------------------------------------------------------------------
---------------------------------------------------------------------------
maop7 - Down 00:01:02:03:04:02 Active

At Switch2
---------------------------------------------------------------------------
---------------------------------------------------------------------------
5 OQ2 2 4 MEP Gi0/2 Enabled
maop2 - Up 00:02:02:03:04:02 Active
maop4 - Up 00:02:02:03:04:02 Active
- - 7 4 MIP Gi0/2 -
- - - 00:02:02:03:04:02 Active
- OQ2 2 4 MIP Gi0/3 -
maop2 - - 00:02:02:03:04:03 Active
At Switch3
---------------------------------------------------------------------------
---------------------------------------------------------------------------
- OQ2 2 4 MIP Gi0/2 -
maop2 - - 00:03:02:03:04:02 Active
maop2 - Up 00:03:02:03:04:03 Active
- - 4 4 MIP Gi0/3 -
- - - 00:03:02:03:04:03 Active
At Switch5

ECFM
---------------------------------------------------------------------------
---------------------------------------------------------------------------
maop7 - Down 00:05:02:03:04:02 Active
At Switch6
---------------------------------------------------------------------------
---------------------------------------------------------------------------
maop2 - Up 00:06:02:03:04:02 Active
maop4 - Up 00:06:02:03:04:02 Active
- - 7 4 MIP Gi0/2 -
- - - 00:06:02:03:04:02 Active
- OQ2 2 4 MIP Gi0/3 -
maop2 - - 00:06:02:03:04:03 Active
At Switch7
---------------------------------------------------------------------------
---------------------------------------------------------------------------
- OQ2 2 4 MIP Gi0/2 -
maop2 - - 00:07:02:03:04:02 Active
maop2 - Up 00:07:02:03:04:03 Active
- - 4 4 MIP Gi0/3 -

- - - 00:07:02:03:04:03 Active
At Switch1, Switch2, Switch3, Switch5, Switch6, Switch7

• Wait for 15 seconds and check for any defect/fault
iss#
Shows no link failure, as no error is detected at any of the bridge.
At Switch1
{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.1 {OCTET STRING} 4F:50:37}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.1 INTEGER 7}

{1.3.6.1.4.1.2076.160.1.0.5.1.4.0.1.1 {OCTET STRING} 6D:61:6F:70:37}
{1.3.6.1.4.1.2076.160.1.0.5.1.2.0.1.1 INTEGER 2}

{1.3.6.1.4.1.2076.160.1.0.7.1.4.0.1.1.1 Unsigned32 0}
{1.3.6.1.4.1.2076.160.1.0.7.1.2.0.1.1.1 INTEGER 2}
{1.3.6.1.4.1.2076.160.1.0.7.1.3.0.1.1.1 INTEGER down}

ECFM

{1.3.6.1.4.1.2076.160.1.0.7.1.5.0.1.1.1 INTEGER true}
% snmp0 get {fsMIEcfmExtMepCciEnabled.0.1.1.1}
{1.3.6.1.4.1.29601.2.13.1.2.3.1.7.0.1.1.1 INTEGER true}
At Switch2
{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.1 {OCTET STRING} 4F:50:37}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.1 INTEGER 7}
{1.3.6.1.4.1.2076.160.1.0.1.1.4.0 INTEGER 4}

{1.3.6.1.4.1.2076.160.1.1.6.1.5.2.7.4 INTEGER active}

{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.2 {OCTET STRING} 4F:50:34}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.2 INTEGER 4}

{1.3.6.1.4.1.2076.160.1.0.5.1.4.0.2.2 {OCTET STRING} 6D:61:6F:70:34}


{1.3.6.1.4.1.2076.160.1.0.5.1.2.0.2.2 INTEGER 4}

{1.3.6.1.4.1.2076.160.1.0.7.1.4.0.2.2.3 Unsigned32 0}
{1.3.6.1.4.1.2076.160.1.0.7.1.2.0.2.2.3 INTEGER 2}
{1.3.6.1.4.1.2076.160.1.0.7.1.3.0.2.2.3 INTEGER up}
{1.3.6.1.4.1.2076.160.1.0.7.1.5.0.2.2.3 INTEGER true}
{1.3.6.1.4.1.2076.160.1.0.1.1.4.0 INTEGER 4}

{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.3 {OCTET STRING} 4F:50:32}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.3 INTEGER 2}

{1.3.6.1.4.1.2076.160.1.0.5.1.4.0.3.3 {OCTET STRING} 6D:61:6F:70:32}
{1.3.6.1.4.1.2076.160.1.0.5.1.2.0.3.3 INTEGER 4}

ECFM
% snmp0 get {fsMIEcfmMaMhfCreation.0.3.3}

{1.3.6.1.4.1.2076.160.1.0.5.1.5.0.3.3 INTEGER defMHFdefault}

{1.3.6.1.4.1.2076.160.1.0.7.1.4.0.3.3.5 Unsigned32 0}
{1.3.6.1.4.1.2076.160.1.0.7.1.2.0.3.3.5 INTEGER 2}
{1.3.6.1.4.1.2076.160.1.0.7.1.3.0.3.3.5 INTEGER up}
{1.3.6.1.4.1.2076.160.1.0.7.1.5.0.3.3.5 INTEGER true}

{1.3.6.1.4.1.2076.160.1.1.6.1.5.3.2.4 INTEGER active}

{1.3.6.1.4.1.29601.2.13.1.2.3.1.7.0.3.3.5 INTEGER true}

{1.3.6.1.4.1.29601.2.13.1.2.3.1.7.0.2.2.3 INTEGER true}
At Switch3
{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.1 {OCTET STRING} 4F:50:34}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.1 INTEGER 4}


{1.3.6.1.4.1.2076.160.1.0.1.1.4.0 INTEGER 2}

{1.3.6.1.4.1.2076.160.1.1.6.1.5.3.4.4 INTEGER active}

{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.2 {OCTET STRING} 4F:50:32}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.2 INTEGER 2}

{1.3.6.1.4.1.2076.160.1.0.5.1.4.0.2.2 {OCTET STRING} 6D:61:6F:70:32}
{1.3.6.1.4.1.2076.160.1.0.5.1.2.0.2.2 INTEGER 4}

{1.3.6.1.4.1.2076.160.1.0.7.1.4.0.2.2.6 Unsigned32 0}
{1.3.6.1.4.1.2076.160.1.0.7.1.2.0.2.2.6 INTEGER 3}
{1.3.6.1.4.1.2076.160.1.0.7.1.3.0.2.2.6 INTEGER up}
{1.3.6.1.4.1.2076.160.1.0.7.1.5.0.2.2.6 INTEGER true}

ECFM

{1.3.6.1.4.1.2076.160.1.1.6.1.5.2.2.4 INTEGER active}

{1.3.6.1.4.1.29601.2.13.1.2.3.1.7.0.2.2.6 INTEGER true}
At Switch5
{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.1 {OCTET STRING} 4F:50:37}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.1 INTEGER 7}

{1.3.6.1.4.1.2076.160.1.0.5.1.4.0.1.1 {OCTET STRING} 6D:61:6F:70:37}
{1.3.6.1.4.1.2076.160.1.0.5.1.2.0.1.1 INTEGER 2}

{1.3.6.1.4.1.2076.160.1.0.7.1.4.0.1.1.2 Unsigned32 0}
{1.3.6.1.4.1.2076.160.1.0.7.1.2.0.1.1.2 INTEGER 2}
{1.3.6.1.4.1.2076.160.1.0.7.1.3.0.1.1.2 INTEGER down}
{1.3.6.1.4.1.2076.160.1.0.7.1.5.0.1.1.2 INTEGER true}
{1.3.6.1.4.1.29601.2.13.1.2.3.1.7.0.1.1.2 INTEGER true}

At Switch6
{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.1 {OCTET STRING} 4F:50:37}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.1 INTEGER 7}
{1.3.6.1.4.1.2076.160.1.0.1.1.4.0 INTEGER 4}

{1.3.6.1.4.1.2076.160.1.1.6.1.5.2.7.4 INTEGER active}

{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.2 {OCTET STRING} 4F:50:34}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.2 INTEGER 4}

{1.3.6.1.4.1.2076.160.1.0.5.1.4.0.2.2 {OCTET STRING} 6D:61:6F:70:34}
{1.3.6.1.4.1.2076.160.1.0.5.1.2.0.2.2 INTEGER 4}

ECFM

{1.3.6.1.4.1.2076.160.1.0.7.1.4.0.2.2.4 Unsigned32 0}
{1.3.6.1.4.1.2076.160.1.0.7.1.2.0.2.2.4 INTEGER 2}
{1.3.6.1.4.1.2076.160.1.0.7.1.3.0.2.2.4 INTEGER up}
{1.3.6.1.4.1.2076.160.1.0.7.1.5.0.2.2.4 INTEGER true}
{1.3.6.1.4.1.2076.160.1.0.1.1.4.0 INTEGER 4}

{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.3 {OCTET STRING} 4F:50:32}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.3 INTEGER 2}

{1.3.6.1.4.1.2076.160.1.0.5.1.4.0.3.3 {OCTET STRING} 6D:61:6F:70:32}
{1.3.6.1.4.1.2076.160.1.0.5.1.2.0.3.3 INTEGER 4}


{1.3.6.1.4.1.2076.160.1.0.7.1.4.0.3.3.5 Unsigned32 0}
{1.3.6.1.4.1.2076.160.1.0.7.1.2.0.3.3.5 INTEGER 2}
{1.3.6.1.4.1.2076.160.1.0.7.1.3.0.3.3.5 INTEGER up}
{1.3.6.1.4.1.2076.160.1.0.7.1.5.0.3.3.5 INTEGER true}

{1.3.6.1.4.1.2076.160.1.1.6.1.5.3.2.4 INTEGER active}

{1.3.6.1.4.1.29601.2.13.1.2.3.1.7.0.3.3.5 INTEGER true}

{1.3.6.1.4.1.29601.2.13.1.2.3.1.7.0.2.2.4 INTEGER true}
At Switch7
{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.1 {OCTET STRING} 4F:50:34}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.1 INTEGER 4}
{1.3.6.1.4.1.2076.160.1.0.1.1.4.0 INTEGER 2}

ECFM

{1.3.6.1.4.1.2076.160.1.1.6.1.5.3.4.4 INTEGER active}

{1.3.6.1.4.1.2076.160.1.0.4.1.3.0.2 {OCTET STRING} 4F:50:32}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.0.2 INTEGER 2}

{1.3.6.1.4.1.2076.160.1.0.5.1.4.0.2.2 {OCTET STRING} 6D:61:6F:70:32}
{1.3.6.1.4.1.2076.160.1.0.5.1.2.0.2.2 INTEGER 4}

{1.3.6.1.4.1.2076.160.1.0.7.1.4.0.2.2.6 Unsigned32 0}
{1.3.6.1.4.1.2076.160.1.0.7.1.2.0.2.2.6 INTEGER 3}
{1.3.6.1.4.1.2076.160.1.0.7.1.3.0.2.2.6 INTEGER up}
{1.3.6.1.4.1.2076.160.1.0.7.1.5.0.2.2.6 INTEGER true}

{1.3.6.1.4.1.2076.160.1.1.6.1.5.2.2.4 INTEGER active}


{1.3.6.1.4.1.29601.2.13.1.2.3.1.7.0.2.2.6 INTEGER true}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.1.1.1 {OCTET STRING} 00}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.2.2.3 {OCTET STRING} 00}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.3.3.5 {OCTET STRING} 00}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.2.2.6 {OCTET STRING} 00}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.1.1.2 {OCTET STRING} 00}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.2.2.4 {OCTET STRING} 00}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.3.3.5 {OCTET STRING} 00}
5.2.8 Shutdown interface
This section desribes the configuration of interface P2 to raise a defect/fault in sample topology.

ECFM
At Switch5
• Make interface P2 as down
At Switch5
• Make interface P2 as down. [Index: Interface Number = 2]
This section describes the verification of generated CCM errors.
At Switch1
MEP-ID : 1
----- ---- ------- -------------------
At Switch2
iss#
Shows no link failure, as no error is detected at Switch2

At Switch3
iss#
At Switch5
MEP-ID : 2
----- ---- ------- -------------------
At Switch6
iss#
At Switch7
iss#
At Switch1
{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.1.1.1 {OCTET STRING} 20}

ECFM
At Switch2
{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.2.2.3 {OCTET STRING} 00}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.3.3.5 {OCTET STRING} 00}
Shows no link failure, as no error is detected at Switch 2
At Switch3
{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.2.2.6 {OCTET STRING} 00}
At Switch5
{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.1.1.2 {OCTET STRING} 20}
At Switch6
{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.2.2.4 {OCTET STRING} 00}
[
Index: ContextID = 0, MD-Index = 3, MA-Index = 3, MEP-ID = 5]
{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.3.3.5 {OCTET STRING} 00}

At Switch7
{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.2.2.6 {OCTET STRING} 00}
This section describes the initiation of loop back and link trace messages to verify and isolate fault.

At Switch1
• Initiate Traceroute to isolate any link failure (error/fault/defect).
with vlanId 2
---------------------------------------------------------------------------
---------------------------------------------------------------------------
1 00:02:02:03:04:01:00:02 00:02:02:03:04:02 IngOK RlyFDB
00:06:02:03:04:01:00:02 - EgrOK Forwarded
2 00:06:02:03:04:01:00:02 00:00:00:00:00:00 RlyFDB
- EgrOK Forwarded
Shows there is a link failure between Switch1 and Switch5, as no reply is received with Relay Action
as RlyHit.
• Initiate the LoopBack Transaction to verify any link failure (error/fault/defect)

Shows there is no link failure between Switch1 and Switch6.

ECFM
• Initiate the LoopBack Transaction to verify any link failure (error/fault/defect)

Shows there is a link failure between Switch6 and Switch5
At Switch1
• Initiate traceroute to isolate any link failure (error/fault/defect). [Index: ContextID = 0, MD-Index = 1,
MA-Index = 1, MEP-ID = 1]
• Walk the Ltrcache Table.

% snmp0 walk x fsMIY1731LtrTable { puts $x }
{1.3.6.1.4.1.29601.2.7.1.2.6.1.3.0.1.1.1.1.1 INTEGER 41}
{1.3.6.1.4.1.29601.2.7.1.2.6.1.3.0.1.1.1.1.2 INTEGER 52}
Shows there is a link failure between Switch1 and Switch5, as data of only first two hops is present in
the Ltrcache.
• Initiate the loopback transaction to MEP on Switch6 for verifying any link failure (error/fault/defect)
• Verify transmission of loopback messages between Switch1 and Switch6. [Index: ContextID = 0, MD-
{1.3.6.1.4.1.2076.160.1.0.7.1.20.0.1.1.1 Unsigned32 1}
% snmp0 get {fsMIEcfmMepTransmitLbmMessages.0.1.1.1}
{1.3.6.1.4.1.2076.160.1.0.7.1.30.0.1.1.1 INTEGER 0}

Shows there is no link failure between Switch1 and Switch6
• Initiate the loopback transaction to MEP on Switch5 for verifying any link failure (error/fault/defect).
{1.3.6.1.4.1.2076.160.1.0.7.1.20.0.1.1.1 Unsigned32 1}
{1.3.6.1.4.1.2076.160.1.0.7.1.30.0.1.1.1 INTEGER 0}
Shows there is link failure between Switch 1 and Switch 5
5.2.11 Bridge UP interface
This section describes the configuration of interface.

At Switch5
• Make interface P2 as up
At Switch5
• Make interface P2 as up. [Index: Interface Number = 2]
This section describes the checking of CCM errors after configuring the interface as up.

ECFM

• Wait for 15 seconds and check if there is any link failure (error/fault/defect), after configuring interface
P2 as up.
iss#
Shows no link failure, as no error is detected.
• Wait for 15 seconds and check if there is any link failure (error/fault/defect), after configuring interface
P2 as up.
{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.1.1.1 {OCTET STRING} 00}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.2.2.3 {OCTET STRING} 00}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.3.3.5 {OCTET STRING} 00}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.2.2.6 {OCTET STRING} 00}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.1.1.2 {OCTET STRING} 00}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.2.2.4 {OCTET STRING} 00}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.3.3.5 {OCTET STRING} 00}

Shows no link failure, as no error is detected.
This section describes the initiation of the loop back and link trace messages to verify and isolate fault.
At Switch1
• Initiate the LoopBack Transaction
• Initiate the LinkTrace Transaction

with vlanId 2
---------------------------------------------------------------------------
---------------------------------------------------------------------------
1 00:02:02:03:04:01:00:02 00:02:02:03:04:02 IngOK RlyFDB
00:06:02:03:04:01:00:02 - EgrOK Forwarded
2 00:06:02:03:04:01:00:02 00:00:00:00:00:00 - RlyFDB
- - EgrOK Forwarded
3 00:05:02:03:04:01:00:02 00:05:02:03:04:02 IngOK RlyHit
- - - Not Forwarded
At Switch1
• Initiate the loopback transaction. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-ID = 1]

ECFM
{1.3.6.1.4.1.2076.160.1.0.7.1.20.0.1.1.1 Unsigned32 1}
{1.3.6.1.4.1.2076.160.1.0.7.1.30.0.1.1.1 INTEGER 0}
Shows no link failure between Switch 1 and Switch 6
• Initiate the linktrace transaction. [Index: ContextID = 0, MD-Index = 1, MA-Index = 1, MEP-ID = 1]

• Walk the Y1731 LTR table.

% snmp0 walk x fsMIY1731LtrTable { puts $x }
{1.3.6.1.4.1.29601.2.7.1.2.6.1.3.0.1.1.1.2.1 INTEGER 29}
{1.3.6.1.4.1.29601.2.7.1.2.6.1.3.0.1.1.1.2.2 INTEGER 43}
{1.3.6.1.4.1.29601.2.7.1.2.6.1.3.0.1.1.1.2.3 INTEGER 109}
Shows no link failure between Switch1 and Switch5, as data of all three hops is present in the
Ltrcache.
5.2.14 Initializing Y.1731
This section describes the enable of Y.1731.
At Switch1, Switch2, Switch3, Switch5, Switch6, and Switch7

• Enable the Y.1731 status.
iss(config)# ethernet cfm y1731 enable
At Switch1, Switch2, Switch3, Switch5, Switch6, and Switch7

• Enable the Y.1731 status. [Index: ContextID = 0]

5.2.15 Checking AIS and LCK features
This section describes the enable of AIS and LCK features.
At Switch6
• Verify CCM errors
• Make interface P3, P4 as down, to raise a defect/fault in sample topology.

• Verify CCM errors.

MEP-ID : 4
----- ---- ------- -------------------
4 4 3 loss of continuity
MEP-ID : 5
----- ---- ------- -------------------
Shows link failure, as error is detected at Switch 6
• Configure client layer level for domain OQ2.

iss(config-ether-ecfm)# client-layer-level 4

ECFM
• Configure AIS capability for MEPID 5.

• Verify whether AIS condition is received at MEPID 4 at level 4 and VLAN 4
MEP-ID : 4
----- ---- ------- -------------------
4 4 - ais condition
MEP-ID : 5
----- ---- ------- -------------------
• Make interface P3, P4 as up, to check if there is any link failure (error/fault/defect).
• Wait for 15 seconds and check link failure (error/fault/defect).

iss#
• Disable AIS capability for MEPID 5.

iss(config-ether-mep)# set ais disable

• Make interface P3 and P4 as down, to raise a defect/fault in sample topology.

• Verify CCM errors at Switch 6.

MEP-ID : 4
----- ---- ------- -------------------
MEP-ID : 5
----- ---- ------- -------------------
Shows link failure, as error is detected at Switch 6
• Configure MEPID 5 as out-of-service.

• Verify whether defect for MEPID 4 at level 4 and VLAN 4 is suppressed.

MEP-ID : 4
----- ---- ------- -------------------
4 4 - lck condition

ECFM
MEP-ID : 5
----- ---- ------- -------------------
• Verify whether LCK condition exist for MEPID 4 at level 4 and VLAN 4.
iss# show ethernet cfm maintenance-point local detail mpid 4
-----------------------------------------------------------
MPID: 4 MdLevel: 4 VLAN: 4 Dir: Up
-----------------------------------------------------------
Client MEG Level : Not Configured

Off-Load Status : Disabled
Out-Of-Service (LCK)
--------------------
Status : Un-Locked(In-Service)
Condition : Exist
Remote Defect Indication (RDI)

------------------------------
Capability : Enabled
Period : Not Configured
Loopback (LB)
-------------
Capability : Enabled
Multicast LBM Reception Capability : Disabled
Test Signal (TST)

-----------------
Multicast TST Reception Capability : Disabled
Alarm Indication Signal (AIS)

-----------------------------
Capability : Disabled

Condition : Does not exist
Delay Measurement (DM)

----------------------
One-Way DM Reception Capability : Enabled
One-Way DM Transaction Interval : Not Configured
Dmr Optional Fields : Not Included
Delay Threshold : 200 microseconds
Frame Loss Measurement (LM)

----------------------------
Near-End Loss Threshold : Not Configured
Far-End Loss Threshold : Not Configured
At Switch6
{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.2.2.4 {OCTET STRING} 00}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.3.3.5 {OCTET STRING} 00}




ECFM

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.2.2.4 {OCTET STRING} 20}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.3.3.5 {OCTET STRING} 20}

Shows link failure, as error is detected.
• Configure client layer level for domain OQ2. [Index: ContextID = 0, MD-Index = 3]
• Configure AIS capability for MEPID 5. [Index: ContextID = 0, MD-Index = 3, MA-Index = 3, MEP-ID =
5]
• Verify whether AIS condition is set for MEPID 4 at level 4 and VLAN 4. [Index: ContextID = 0, MD-
% snmp0 get {{fsMIY1731MepAisCondition.0.2.2.4}}
{1.3.6.1.4.1.29601.2.7.1.2.4.1.91.0.2.2.4 INTEGER true}
• Make interface P3, P4 as up, to check if there is any link failure (error/fault/defect).

• Wait for 15 seconds and check link failure (error/fault/defect).

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.2.2.4 {OCTET STRING} 00}


{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.3.3.5 {OCTET STRING} 00}

• Disable AIS capability for MEPID 5. [Index: ContextID = 0, MD-Index = 3, MA-Index = 3, MEP-ID = 5]
% snmp0 set {{fsMIY1731MepAisCapability.0.3.3.5 disabled}}



{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.2.2.4 {OCTET STRING} 20}

{1.3.6.1.4.1.2076.160.1.0.7.1.14.0.3.3.5 {OCTET STRING} 20}

• Configure MEPID 5 as out-of-service. [Index: ContextID = 0, MD-Index = 3, MA-Index = 3, MEP-ID =

5]
• Verify whether LCK condition exist for MEPID 4 at level 4 and VLAN 4. [Index: ContextID = 0, MD-
% snmp0 get {fsMIY1731MepOutOfService.0.3.3.5}
{1.3.6.1.4.1.29601.2.7.1.2.4.1.2.0.3.3.5 INTEGER true}

ECFM
5.3 Configuring ECFM on Provider Backbone Bridges

This section describes the configuration of the ECFM functionality for provider backbone bridges on the
sample topology depicted in the Figure 5-3.
Customer Network
(PCB)
Switch1
P1
Provider Backbone Network P10 BEB
(I-COMP)
Switch2
P9
P18
(B-COMP)
Switch3
P17
P26
Provider Backbone Network BEB
(B-COMP)
Switch4
P27
P36
Bridge
(I-COMP)
PCB Provider Core
Switch5
BEB
Backbone Edge
P33 Entity
P42 Down MEP
Color code
(PCB) Level 7 VLAN 11
Switch6 Internal LAN
Level 6 ISID 300
Figure 5-3: Configuration of ECFM on Provider Backbone bridges

MAC address of ports on the bridges are of form 00:0m:02:03:04:0n, where m is bridge number and n is

Figure 5-3 depicts a topology for a provider backbone bridged network that consists of two customer
bridges (Switch1, Switch6), two I-component bridges (Switch2, Switch5), and two B-component bridges
(Switch3, Switch4). Switches 1 to 6 refer to six virtual contexts of the switch. Maintenance points
(MEP/MIP) are configured at same MD Level, and VLANs are shown by the color code. Port P1, P17, P26
and P42 are configured as PNP (Provider Network Port). P10 and P33 are configured as CNP (Customer
Network Port). P9 is configured as PIP (Provider Instance Port). P18 is configured as CBP (Customer
Bridge Port). In addition, there is an internal LAN between Switch4 and Switch5.
Connectivity is checked between all the bridges (Switch1 to Switch6) through continuity check protocol. A
link failure is intentionally incorporated at P9 of Switch2. Due to this link failure, errors will be detected at
Switch1 and Switch6.
5.3.1 Enabling the Provider Backbone Bridging
This section describes the enabling of the provider backbone bridging.
• Enable the provider backbone bridging

iss(config)# no shutdown provider-backbone-bridge
• Enable the provider backbone bridging. [Index: None]

% snmp0 set {{fsPbbShutdownStatus.0 start}}
5.3.2 Configuring the Default Bridge Mode and Interfaces
This section describes the configuration of default bridge mode and interfaces at virtual contexts.
At Switch1
iss(config)# switch Switch1
iss(config-switch)# no shutdown vlan
iss(config-switch)# set gvrp enable
iss(config-switch)# set gmrp enable

ECFM
iss(config-if)# map switch Switch1
iss(config-if)# end
At Switch2
iss(config-if)# end
At Switch3

iss(config-if)# end
At Switch4
iss(config-if)# end
At Switch5

ECFM
iss(config-if)# end
At Switch6
iss(config-if)# end
At Switch1
• Set bridge-mode as customerBridge [Index: ContextID = 1]

• Create interfaces as up [Index: Interface number = 1]

At Switch2

[Index: Interface number = 10]


ECFM

At Switch3


At Switch4




At Switch5

ECFM


At Switch6


5.3.3 Configuring Provider Bridge Mode
This section describes the configuration of provider bridge mode.

At Switch1
• Configure the bridge mode as provider-core
iss(config-switch)# shutdown spanning-tree
iss(config-switch)# set gvrp disable
iss(config-switch)# set gmrp disable
iss(config-switch)# shutdown garp
iss(config-switch)# bridge-mode provider-core
iss(config-switch)# no shutdown garp
iss(config-switch)#end
At Switch2
• Configure the bridge mode as provider-backbone-icomp
iss(config-switch)# bridge-mode provider-backbone-icomp
At Switch3
• Configure the bridge mode as provider-backbone-bcomp

ECFM

iss(config-switch)# bridge-mode provider-backbone-bcomp
At Switch4
• Configure the bridge mode as provider-backbone-bcomp
At Switch5
• Configure the bridge mode as provider-backbone-icomp
At Switch6


At Switch1
• Configure the bridge mode as providerCoreBridge [Index: ContextID = 1]
At Switch2
• Configure the bridge mode as providerBackoneICompBridge [Index: ContextID = 2]
% snmp0 set {{fsMIRstSystemControl.2 shutdown}}
% snmp0 set {{fsMIRstModuleStatus.2 enabled}}
At Switch3
• Configure the bridge mode as providerBackoneBCompBridge [Index: ContextID = 3]

ECFM

% snmp0 set {{fsMIVlanBridgeMode.3 providerBackoneBCompBridge}}
% snmp0 set {{fsMIMstSystemControl.3 started}}
At Switch4
• Configure the bridge mode as providerBackoneBCompBridge [Index: ContextID = 4]
% snmp0 set {{fsMIMstSystemControl.4 enabled}}
At Switch5
• Configure the bridge mode as providerBackoneICompBridge [Index: ContextID = 5]
% snmp0 set {{fsMIRstSystemControl.5 start}}
At Switch6
% snmp0 set {{fsDot1qGvrpStatus.6 disbaled}}


This section describes the initialization of the ECFM on all the switches.
• Initialize ECFM on all switches



ECFM
5.3.5 Configuring Interface Type
This section describes the configuration of the interface type.
At Switch1
• Configure port type of port P1 as PNP
iss(config-if)# end
At Switch2
• Configure port type of port P9 as PIP


iss(config-if)# port-type providerInstancePort
• Configure port type of port P10 as CNP

iss(config-if)# bridge port-type customerNetworkPort s-tagged
iss(config-if)# end
At Switch3
• Configure port type of port P18 as CBP
iss(config-if)# bridge port-type customerBackbonePort
iss(config-if)# end

iss(config-if)# end
At Switch4

ECFM
iss(config-if)# end
• Create a virtual port and configure its port type as CBP

iss(config)# interface virtual 1
iss(config-if)# end
At Switch5
• Configure port type of port P33 as CNP s-tagged
iss(config-if)# end
• Create a virtual port and configure its port type as PIP

iss(config-if)# end
At Switch6
• Configure port type of ports and P42 as PNP
iss(config-if)# end

At Switch1
• Configure port type of port P1 as PNP [Index: Interface number = 1]
At Switch2
• Configure port type of port P9 as PIP [Index: Interface number = 9]
% snmp0 set {{ifMainBrgPortType.9 providerInstancePort}}
• Configure port type of port P10 as CNP [Index: Interface number = 10]
% snmp0 set {{ifMainBrgPortType.10 customerNetworkPortStagged}}
At Switch3
• Configure port type of port P18 as CBP [Index: Interface number = 18]
% snmp0 set {{ifMainBrgPortType.18 customerBackbonePort}}
At Switch4
• Create a virtual port and configure its port type as CBP [Index: Interface number =5195]
% snmp0 set {{ifMainRowStatus.5195 5}}
% snmp0 set {{ifAlias.5195 virtual2}}
% snmp0 set {{ifMainType.5195 brgPort}}
% snmp0 set {{fsVcIfRowStatus.5195 createAndWait }}

ECFM
At Switch5
• Configure port type of port P33 as CNP s-tagged [Index: Interface number = 33]
• Create a virtual port and configure its port type as PIP [Index: Interface number = 5196]
% snmp0 set {{ifMainRowStatus.5196 5}}
% snmp0 set {{ifMainType.5196 pip}}
At Switch6
5.3.6 Configuring VLAN and VLAN-mapping
This section describes the configuration of VLAN and VLAN mappings on respective switches.
At Switch1
• Create VLAN 11 and make interfaces P1 as member port of this VLAN
iss(config-switch-vlan)# ports gigabitethernet 0/1
At Switch2

At Switch3
• Create BVLAN 10 and make interfaces P17 and P18 as member port of this VLAN
iss(config-switch-vlan)# ports gigabitethernet 0/17,0/18 untagged gigabitethernet 0/18
At Switch4
• Create BVLAN 10 and make virtual port as member port of this VLAN
iss(config-switch-vlan)# ports gigabitethernet 0/26 virtual 1 untagged virtual 1
At Switch5
At Switch6
• Create VLAN 11 and make interface P42 as member port of this VLAN

ECFM
At Switch1
• Create VLAN 11 and make interfaces P1 as member port of this VLAN [Index: ContextID =1, VLAN-
ID= 11]
[Index: ContextID =1, VLAN-ID= 11, Interface number = 1]

At Switch2
ID= 11]
At Switch3
• Create BVLAN 10 and make interfaces P17 and P18 as member port of this VLAN [Index: ContextID
=3, VLAN-ID= 10]
Index: ContextID =3, VLAN-ID= 10, Interface number = 17]

Index: ContextID =3, VLAN-ID= 10, Interface number = 18]

At Switch4
• Create BVLAN 10 and make virtual port as member port of this VLAN [Index: ContextID = 4, VLAN-
ID= 10]
[Index: ContextID = 4, VLAN-ID= 10, Interface number = 26]



At Switch5
ID= 11]

At Switch6
• Create VLAN 11 and make interface P42 as member port of this VLAN [Index: ContextID =6, VLAN-
ID= 11]

5.3.7 Configuring ECFM and PBB
This section describes the configuration of ECFM and PBB.
At Switch1
• Create down MEP at interface P1 of Level 7 and Vlan 11
iss(config-switch)# ethernet cfm domain name md7 level 7
iss(config-ether-ecfm)# service name ma7 vlan 11

ECFM
iss# show ethernet cfm maintenance-point local mep interface gigabitethernet 0/1 switch
Switch1
Switch Switch1
---------------------------------------------------------------------------
---------------------------------------------------------------------------
1 md7 7 11 MEP Gi0/1 Disabled
ma7 - Down 00:01:02:03:04:01 Active
At Switch2
• Configure service instance 300 and map port P9 to it. Also configure SVLAN mapping to map s-vlan
11 to ISID 300 with untagged-pip as false
iss(config-switch)# service instance 300
iss(config-switch-si)# ports icomp gigabitethernet 0/9
iss(config-switch-si)# service-instance map untagged-pip false vlan 11
iss(config-switch-si)# no shutdown
iss(config-switch-si)# set service-instance status enable
iss(config-switch-si)#end
• Configure service instance 300 as PISID of interface 10

iss(config-if)# switchport pisid 300
iss(config)# end
iss#
• Create up MEP of level 6 and ISID 300 at interface P10

iss(config)# switch switch2


iss(config-ether-ecfm)# service name ma6 service-instance 300
iss(config-ether-ecfm)# mep crosscheck mpid 3 service-instance 300
iss(config-if)# ethernet cfm mep level 6 inward mpid 3 service-instance 300 active
switch2
Switch switch2
---------------------------------------------------------------------------
---------------------------------------------------------------------------
3 md6 6 - MEP Gi0/10 Disabled
ma6 300 Up 00:01:02:03:04:0a Active
At Switch3
• Configure service instance 300 and map port P18 to it. Also configure BVLAN mapping to map b-vlan
10 to ISID 300
iss(config-switch-si)# ports bcomp gigabitethernet 0/18
iss(config-switch-si)# member-ports vlan 10 gigabitethernet 0/18
iss(config-switch-si)# end
At Switch4
• Map virtual port 1 to service instances 300
iss(config-switch-si)# ports bcomp virtual 1

ECFM
iss(config-switch-si)# member-ports vlan 10 virtual 1

At Switch5
• Configure service instance 300 and map virtual port 2 to it. Also configure SVLAN mapping to map s-
vlan 11 to ISID 300 with untagged-pip as false
iss(config-switch-si)# ports icomp virtual 2
• Create connection between PIP and CBP of Switch4 and Switch5 respectively
iss(config)# internal-lan 1 add interface virtual 1,2
iss(config-if)# end

iss(config-if)# switchport pisid 300
iss(config)# end

iss#
• Create up MEP of level 6 and ISID 300 at interface P33.

iss(config-if)# ethernet cfm mep level 6 inward mpid 4 service-instance 300 active
switch5
Switch switch5
---------------------------------------------------------------------------
---------------------------------------------------------------------------
ma6 300 Up 00:01:02:03:04:21 Active
At Switch6

ECFM

Switch6
Switch Switch6
---------------------------------------------------------------------------
---------------------------------------------------------------------------
ma7 - Down 00:01:02:03:04:2a Active
At Switch1
Create the Maintenance Domain [Index: ContextID =1, MD-Index = 1]
% snmp0 set {{fsMIEcfmMdName.1.1 6D:64:37}}
Create the Maintenance Association [Index: ContextID =1, MD-Index = 1, MA-Index = 1]

% snmp0 set {{fsMIEcfmMaName.1.1.1 6D:61:37}}
Configure MEP list [Index: ContextID =1, MD-Index = 1, MA-Index = 1, MEP-ID = 1]

[Index: ContextID =1, MD-Index = 1, MA-Index = 1, MEP-ID = 2]


Configure the MEP [Index: ContextID =1, MD-Index = 1, MA-Index = 1, MEP-ID = 1]

• Display MEP configuration at interface P1 of Level 7 and Vlan 11 [Index: ContextID =1, MD-Index = 1]
% snmp0 get {fsMIEcfmMdName.1.1} [Index: ContextID =1, MD-Index = 1]

{1.3.6.1.4.1.2076.160.1.0.4.1.3.1.1 {OCTET STRING} 6D:64:37}
% snmp0 get {fsMIEcfmMdMdLevel.1.1} [Index: ContextID =1, MD-Index = 1]

{1.3.6.1.4.1.2076.160.1.0.4.1.4.1.1 INTEGER 7}
% snmp0 get {fsMIEcfmMaFormat.1.1.1} [Index: ContextID =1, MD-Index = 1, MA-Index = 1]

% snmp0 get {fsMIEcfmMaName.1.1.1} [Index: ContextID =1, MD-Index = 1, MA-Index = 1]

{1.3.6.1.4.1.2076.160.1.0.5.1.4.1.1.1 {OCTET STRING} 6D:61:37}
% snmp0 get {fsMIEcfmMaCcmInterval.1.1.1} [Index: ContextID =1, MD-Index = 1, MA-Index = 1]

% snmp0 get {fsMIEcfmMaPrimaryVlanId.1.1.1} [Index: ContextID =1, MD-Index = 1, MA-Index = 1]

{1.3.6.1.4.1.2076.160.1.0.5.1.2.1.1.1 INTEGER 11}
% snmp0 get {fsMIEcfmMepPrimaryVid.1.1.1.1} [Index: ContextID =1, MD-Index = 1, MA-Index = 1,

MEP-ID = 1]
{1.3.6.1.4.1.2076.160.1.0.7.1.4.1.1.1.1 Unsigned32 0}
% snmp0 get {fsMIEcfmMepIfIndex.1.1.1.1} [Index: ContextID =1, MD-Index = 1, MA-Index = 1,

MEP-ID = 1]
{1.3.6.1.4.1.2076.160.1.0.7.1.2.1.1.1.1 INTEGER 1}
% snmp0 get {fsMIEcfmMepDirection.1.1.1.1} [Index: ContextID =1, MD-Index = 1, MA-Index = 1,

MEP-ID = 1]
{1.3.6.1.4.1.2076.160.1.0.7.1.3.1.1.1.1 INTEGER down}
% snmp0 get {fsMIEcfmMepActive.1.1.1.1} [Index: ContextID =1, MD-Index = 1, MA-Index = 1,

MEP-ID = 1]

ECFM
{1.3.6.1.4.1.2076.160.1.0.7.1.5.1.1.1.1 INTEGER true}
At Switch2
11 to ISID 300 with untagged-pip as false [Index: Interface number = 5255]
% snmp0 set {{ifMainBrgPortType.5255 virtualInstancePort}}
[Index: ContextID = 2, Interface number = 5255]

% snmp0 set {{fsPbbVipRowStatus.2.5255 createAndWait }}
% snmp0 set {{fsPbbVipISid.2.5255 Unsigned32 300}}
% snmp0 set {{fsPbbVipToPipMappingRowStatus.2.5255 createAndWait }}
% snmp0 set {{fsPbbVipToPipMappingPipIfIndex.2.5255 9}}
% snmp0 set {{fsPbbVipToPipMappingRowStatus.2.5255 active}}
% snmp0 set {{fsPbbVipRowStatus.2.5255 active}}
[Index: ContextID = 2, VLAN-ID = 11, Interface number = 5255]

• Create up MEP of level 6 and ISID 300 at interface P10.
• Create the maintenance domain [Index: ContextID =2, MD-Index = 1]

% snmp0 set {{fsMIEcfmMdFormat.2.1 4}}
• Create the maintenance association [Index: ContextID =2, MD-Index = 1, MA-Index = 1,

ServiceSelectorType = 2, ISID = 300]

% snmp0 set {{fsMIEcfmExtMaRowStatus.2.1.1.2.300 createAndWait}}

% snmp0 set {{fsMIEcfmExtMaFormat.2.1.1.2.300 2}}
% snmp0 set {{fsMIEcfmExtMaName.2.1.1.2.300 6D:61:36}}
% snmp0 set {{fsMIEcfmExtMaCcmInterval.2.1.1.2.300 4}}
% snmp0 set {{fsMIEcfmExtMaRowStatus.2.1.1.2.300 active}}
• Configure MEP list


• Configure the MEP [Index: ContextID =2, MD-Index = 1, MA-Index = 1, MEP-ID = 3]

% snmp0 set {{fsMIEcfmExtMepRowStatus.2.1.1.3 createAndWait}}
% snmp0 set {{fsMIEcfmExtMepPrimaryVidOrIsid.2.1.1.3 300}}
% snmp0 set {{fsMIEcfmExtMepIfIndex.2.1.1.3 10}}
% snmp0 set {{fsMIEcfmExtMepDirection.2.1.1.3 up}}
% snmp0 set {{fsMIEcfmExtMepActive.2.1.1.3 true}}
% snmp0 set {{fsMIEcfmExtMepRowStatus.2.1.1.3 active}}
• View MEP configuration at interface P10

[Index: ContextID =2, MD-Index = 1]

{1.3.6.1.4.1.2076.160.1.0.4.1.3.2.1 {OCTET STRING} 6D:64:36}

{1.3.6.1.4.1.2076.160.1.0.4.1.4.2.1 INTEGER 6}
[Index: ContextID =2, MD-Index = 1, MA-Index = 1, ServiceSelectorType = 1, ISID = 4395]

% snmp0 get {fsMIEcfmExtMaFormat.2.1.1.1.4395}
{1.3.6.1.4.1.29601.2.13.1.2.2.1.4.2.1.1.1.4395 INTEGER charString}
% snmp0 get {fsMIEcfmExtMaName.2.1.1.1.4395}

{1.3.6.1.4.1.29601.2.13.1.2.2.1.5.2.1.1.1.4395 {OCTET STRING} 6D:61:36}

ECFM
% snmp0 get {fsMIEcfmExtMaCcmInterval.2.1.1.1.4395}

{1.3.6.1.4.1.29601.2.13.1.2.2.1.8.2.1.1.1.4395 INTEGER interval1s}
% snmp0 get {fsMIEcfmExtMepIfIndex.2.1.1.3}

{1.3.6.1.4.1.29601.2.13.1.2.3.1.2.2.1.1.3 INTEGER 10}
% snmp0 get {fsMIEcfmExtMepDirection.2.1.1.3}

{1.3.6.1.4.1.29601.2.13.1.2.3.1.3.2.1.1.3 INTEGER up}
% snmp0 get {fsMIEcfmExtMepActive.2.1.1.3}

{1.3.6.1.4.1.29601.2.13.1.2.3.1.5.2.1.1.3 INTEGER true}
• Configure service instance 300 as PISID of interface 10. [Index: ContextID = 2, Interface number = 10
]
% snmp0 set {{fsPbbPIsidRowStatus.2.10 createAndWait}}
% snmp0 set {{fsPbbPortPisid.2.10 300}}
% snmp0 set {{fsPbbPIsidRowStatus.2.10 active}}
At Switch3
• Configure service instance 300 and map port P18 to it. Also configure BVLAN mapping to map b-vlan
10 to ISID 300 [Index: ContextID =3, Interface number = 18, ISID = 300]
% snmp0 set {{fsPbbCBPServiceMappingRowStatus.3.18.300 createAndWait}}
% snmp0 set {{fsPbbCBPServiceMappingBVid.3.18.300 10}}
% snmp0 set {{fsPbbCBPServiceMappingRowStatus.3.18.300 active}}
[Index: ContextID =3, VLAN-ID = 10]

[Index: ContextID =3, VLAN-ID = 10, Interface number = 17]


At Switch4
• Map virtual port 1 to service instances 300 [Index: ContextID = 4, Interface number = 5195, ISID =
300]

At Switch5
• Configure service instance 300 and map virtual port 2 to it. Also, configure SVLAN mapping to map s-
vlan 11 to ISID 300 with untagged-pip as false
% snmp0 set {{ifMainRowStatus.5256 createAndWait }}

% snmp0 set {{fsPbbVipToPipMappingRowStatus.5.5256 5}}

• Create connection between PIP and CBP of Switch4 and Switch5 respectively
Create an ILAN interface
% snmp0 set {{ifAlias.5270 "internal-lan1"}}
% snmp0 set {{ifMainType.5270 ilan}}
Set the Adminstatus of both PIP and CBP as down


ECFM

Create the Stack Entries

[Index: Interface number = 5195], I-LAN = 5270]
% snmp0 set {{ifStackStatus.5195.5270 createAndWait}}
% snmp0 set {{ifStackStatus.5196.5270 createAndWait}}
Set the Stack Status as active

% snmp0 set {{ifStackStatus.5195.5270 active}}
% snmp0 set {{ifStackStatus.5196.5270 active}}
Set the Adminstatus of both PIP and CBP back to UP

[Index: Interface number = 5195]]

• Create up MEP of level 6 and ISID 300 at interface P33

• Create the maintenance domain [Index: ContextID =5, MD-Index = 1]
% snmp0 set {{fsMIEcfmMdFormat.5.1 4}}
• Create the maintenance association [Index: ContextID =5, MD-Index = 1, MA-Index = 1,

ServiceSelectorType = 2, ISID = 300]
% snmp0 set {{fsMIEcfmExtMaFormat.5.1.1.2.300 2}}
% snmp0 set {{fsMIEcfmExtMaCcmInterval.5.1.1.2.300 4}}

• Configure MEP list


• Configure the MEP [Index: ContextID =5, MD-Index = 1, MA-Index = 1, MEP-ID = 4]

% snmp0 set {{fsMIEcfmExtMepDirection.5.1.1.4 up}}

{1.3.6.1.4.1.2076.160.1.0.4.1.3.5.1 {OCTET STRING} 6D:64:36}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.5.1 INTEGER 6}
[Index: ContextID =5, MD-Index = 1, MA-Index = 1, ServiceSelectorType = 1, ISID = 4395]

% snmp0 get {fsMIEcfmExtMaFormat.5.1.1.1.4395}
{1.3.6.1.4.1.29601.2.13.1.2.2.1.4.5.1.1.1.4395 INTEGER charString}
% snmp0 get {fsMIEcfmExtMaName.5.1.1.1.4395}
{1.3.6.1.4.1.29601.2.13.1.2.2.1.5.5.1.1.1.4395 {OCTET STRING} 6D:61:36}
% snmp0 get {fsMIEcfmExtMaCcmInterval.5.1.1.1.4395}
{1.3.6.1.4.1.29601.2.13.1.2.2.1.8.5.1.1.1.4395 INTEGER interval1s}

% snmp0 get {fsMIEcfmExtMepIfIndex.5.1.1.4}
{1.3.6.1.4.1.29601.2.13.1.2.3.1.2.5.1.1.4 INTEGER 33}

ECFM
% snmp0 get {fsMIEcfmExtMepDirection.5.1.1.4}

{1.3.6.1.4.1.29601.2.13.1.2.3.1.3.5.1.1.4 INTEGER up}
% snmp0 get {fsMIEcfmExtMepActive.5.1.1.4}
{1.3.6.1.4.1.29601.2.13.1.2.3.1.5.5.1.1.4 INTEGER true}

[Index: ContextID = 5, Interface number = 33 ]
% snmp0 set {{fsPbbPIsidRowStatus.5.33 createAndWait}}
% snmp0 set {{fsPbbPortPisid.5.33 300}}
% snmp0 set {{fsPbbPIsidRowStatus.5.33 active}}
At Switch6
Create the Maintenance Domain [Index: ContextID =6, MD-Index = 1]
Create the Maintenance Association [Index: ContextID =6, MD-Index = 1, MA-Index = 1]



Configure MEP [Index: ContextID =6, MD-Index = 1, MA-Index = 1, MEP-ID = 2]


% snmp0 set {{fsMIEcfmMepDirection.6.1.1.2 1}}
% snmp0 set {{fsMIEcfmMepActive.6.1.1.2 1}}
• Display MEP configuration at interface P1 of Level 7 and Vlan 11 [Index: ContextID =6, MD-Index = 1]
% snmp0 get {fsMIEcfmMdName.6.1} [Index: ContextID =6, MD-Index = 1]

{1.3.6.1.4.1.2076.160.1.0.4.1.3.6.1 {OCTET STRING} 6D:64:37}
% snmp0 get {fsMIEcfmMdMdLevel.6.1} [Index: ContextID =6, MD-Index = 1]

{1.3.6.1.4.1.2076.160.1.0.4.1.4.6.1 INTEGER 7}
% snmp0 get {fsMIEcfmMaFormat.6.1.1} [Index: ContextID =6, MD-Index = 1, MA-Index = 1]

% snmp0 get {fsMIEcfmMaName.6.1.1} [Index: ContextID =6, MD-Index = 1, MA-Index = 1]

{1.3.6.1.4.1.2076.160.1.0.5.1.4.6.1.1 {OCTET STRING} 6D:61:37}
% snmp0 get {fsMIEcfmMaCcmInterval.6.1.1} [Index: ContextID =6, MD-Index = 1, MA-Index = 1]

% snmp0 get {fsMIEcfmMaPrimaryVlanId.6.1.1} [Index: ContextID =6, MD-Index = 1, MA-Index = 1]

{1.3.6.1.4.1.2076.160.1.0.5.1.2.6.1.1 INTEGER 11}
% snmp0 get {fsMIEcfmMepPrimaryVid.6.1.1.2} [Index: ContextID =6, MD-Index = 1, MA-Index = 1,

MEP-ID = 2]
{1.3.6.1.4.1.2076.160.1.0.7.1.4.6.1.1.2 Unsigned32 0}
% snmp0 get {fsMIEcfmMepIfIndex.6.1.1.2} [Index: ContextID =6, MD-Index = 1, MA-Index = 1,

MEP-ID = 3]
{1.3.6.1.4.1.2076.160.1.0.7.1.2.6.1.1.2 INTEGER 42}

ECFM
% snmp0 get {fsMIEcfmMepDirection.6.1.1.2} [Index: ContextID =6, MD-Index = 1, MA-Index = 1,

MEP-ID = 1]
{1.3.6.1.4.1.2076.160.1.0.7.1.3.6.1.1.2 INTEGER down}
% snmp0 get {fsMIEcfmMepActive.6.1.1.2} [Index: ContextID =6, MD-Index = 1, MA-Index = 1,

MEP-ID = 1]
{1.3.6.1.4.1.2076.160.1.0.7.1.5.6.1.1.2 INTEGER true}
5.3.8 Detecting Fault
This section describes the enabling of CC for detecting fault.

iss(config-switch)# ethernet cfm cc enable level 6 service-instance 300

Switch default
Switch Switch1
Switch Switch2

Switch Switch3
Switch Switch4
Switch Switch5
Switch Switch6
iss#
At Switch2
• Make interface P10 as down, to raise a defect/fault in sample topology

Switch default
Switch switch1
MEP-ID : 1
----- ---- ------- -------------------
Switch switch2
MEP-ID : 3
Level ISID RMEP-ID Current defect type
----- ---- ------- -------------------
Switch switch3

ECFM
Switch switch4
Switch switch5
MEP-ID : 4
Level ISID RMEP-ID Current defect type
----- ---- ------- -------------------
Switch switch6
MEP-ID : 2
----- ---- ------- -------------------


% snmp0 set {{fsMIEcfmExtMepRowStatus.2.1.1.3 notInService}}


% snmp0 set {{fsMIEcfmExtMepRowStatus.5.1.1.4 notInService}}


• Wait for 15 seconds to check for any defect/fault
{1.3.6.1.4.1.29601.2.13.1.2.3.1.14.1.1.1.1 {OCTET STRING} 00}

{1.3.6.1.4.1.29601.2.13.1.2.3.1.14.6.1.1.2 {OCTET STRING} 00}

{1.3.6.1.4.1.29601.2.13.1.2.3.1.14.2.1.1.3 {OCTET STRING} 00}

{1.3.6.1.4.1.29601.2.13.1.2.3.1.14.5.1.1.4 {OCTET STRING} 00}
At Switch2
• Make interface P10 as down, to raise a defect/fault in sample topology
{1.3.6.1.4.1.29601.2.13.1.2.3.1.14.1.1.1.1 {OCTET STRING} 20}

{1.3.6.1.4.1.29601.2.13.1.2.3.1.14.6.1.1.2 {OCTET STRING} 20}


ECFM
{1.3.6.1.4.1.29601.2.13.1.2.3.1.14.2.1.1.3 {OCTET STRING} 80}

{1.3.6.1.4.1.29601.2.13.1.2.3.1.14.5.1.1.4 {OCTET STRING} 40}
This section describes the initiation of loopback to verify the defect location.
Loopback from Switch6

• Initiate the loopback transaction from MEP at Switch6 to MEP at Switch1
iss# ping ethernet mac 00:01:02:03:04:01 level 7 vlan 11 count 1 switch Switch6
Shows link failure between the Switch1 and Switch6.

• Initiate the loopback transaction from MEP at Switch5 to MEP at Switch2.
iss# ping ethernet mac 00:01:02:03:04:0A level 6 service-instance 300 count 1 switch switch5
Shows link success between Switch5 and Switch2.
Linktrace from Switch6

• Initiate the linktrace transaction from MEP at Switch6 to MEP at Switch1
iss#
iss# traceroute ethernet mac 00:01:02:03:04:01 level 7 vlan 11 switch switch6
No traceroute reply received
Shows link failure between Switch1 and Switch6.


• Initiate the linktrace transaction from MEP at Switch5 to MEP at Switch2.
iss# traceroute ethernet mac 00:01:02:03:04:0A level 6 service-instance 300 switch switch5
Traceroute to Macaddress 00:01:02:03:04:0a in domain md6 at level 6
with Isid 300
--------------------------------------------------------------------------
---------------------------------------------------------------------------
1 00:01:02:03:04:06:00:21 - - RlyHit
00:01:02:03:04:01:00:0a 00:01:02:03:04:0a EgrBlocked Terminal MEP

• Initiate the loopback transaction from MEP at Switch6 to MEP at Switch1. [Index: ContextID =6, MD-
% snmp0 set {{fsMIEcfmMepTransmitLbmDataTlv.6.1.1.2 74:65:73:74:69:6E:67}}
• Verify the loopback messages transmitted between the Switch5 and Switch6. [Index: ContextID =6,
MD-Index = 1, MA-Index = 1, MEP-ID = 2]

{1.3.6.1.4.1.2076.160.1.0.7.1.20.6.1.1.2 Unsigned32 0}

{1.3.6.1.4.1.2076.160.1.0.7.1.30.6.1.1.2 INTEGER 0}
Shows link failure between the Switch1 and Switch6.

ECFM

• Initiate the loopback transaction from MEP at Switch5 to MEP at Switch2. [Index: ContextID =5, MD-
% snmp0 set {{fsMIEcfmExtMepTransmitLbmMessages.5.1.1.4 1}}
% snmp0 set {{fsMIEcfmExtMepTransmitLbmDestMacAddress.5.1.1.4 00:01:02:03:04:0A}}
% snmp0 set {{fsMIEcfmExtMepTransmitLbmDestIsMepId.5.1.1.4 false}}
% snmp0 set {{fsMIEcfmExtMepTransmitLbmDataTlv.5.1.1.4 74:65:73:74:69:6E:67}}
% snmp0 set {{fsMIEcfmExtMepTransmitLbmStatus.5.1.1.4 transmit}}
• Verify the loopback messages transmitted between the Switch5 and Switch2. [Index: ContextID =5,
MD-Index = 1, MA-Index = 1, MEP-ID = 4]
% snmp0 get {fsMIEcfmExtMepLbrIn.5.1.1.4}
{1.3.6.1.4.1.29601.2.13.1.2.3.1.20.5.1.1.4 Unsigned32 3}
% snmp0 get {fsMIEcfmExtMepTransmitLbmMessages.5.1.1.4}
{1.3.6.1.4.1.29601.2.13.1.2.3.1.30.5.1.1.4 INTEGER 0}
Shows link success between the Switch5 and Switch2.

• Initiate the linktrace transaction from MEP at Switch6 to MEP at Switch1
[Index: ContextID =6]
% snmp0 set {{ fsMIEcfmLtrCacheStatus.6 enabled}}

% snmp0 set {{ fsMIEcfmMepTransmitLtmTargetMacAddress.6.1.1.2 00:01:02:03:04:01}}
% snmp0 set {{ fsMIEcfmMepTransmitLtmTargetIsMepId.6.1.1.2 false}}
% snmp0 set {{ fsMIEcfmMepTransmitLtmStatus.6.1.1.2 transmit}}
• Walk the Link Trace Table

Shows link failure between the Switch1 and Switch6, as no value is displayed in the walk

• Initiate the linktrace transaction from MEP at Switch5 to MEP at Switch2.
[Index: ContextID =5]
% snmp0 set {{ fsMIEcfmLtrCacheStatus.5 enabled}}


% snmp0 set {{ fsMIEcfmExtMepTransmitLtmTargetMacAddress.5.1.1.4 00:01:02:03:04:0A}}
% snmp0 set {{ fsMIEcfmExtMepTransmitLtmTargetIsMepId.5.1.1.4 false}}
% snmp0 set {{ fsMIEcfmExtMepTransmitLtmStatus.5.1.1.4 transmit}}
• Walk the Link Trace Table.

{1.3.6.1.4.1.2076.160.1.0.8.1.3.5.1.1.4.1.1 Unsigned32 63}
{1.3.6.1.4.1.2076.160.1.0.8.1.4.5.1.1.4.1.1 INTEGER false}
{1.3.6.1.4.1.2076.160.1.0.8.1.5.5.1.1.4.1.1 INTEGER true}
{1.3.6.1.4.1.2076.160.1.0.8.1.6.5.1.1.4.1.1 {OCTET STRING}
00:01:02:03:04:06:00:21}
{1.3.6.1.4.1.2076.160.1.0.8.1.7.5.1.1.4.1.1 {OCTET STRING}
00:01:02:03:04:01:00:0A}
{1.3.6.1.4.1.2076.160.1.0.8.1.8.5.1.1.4.1.1 INTEGER rlyHit}
{1.3.6.1.4.1.2076.160.1.0.8.1.9.5.1.1.4.1.1 INTEGER 0}
{1.3.6.1.4.1.2076.160.1.0.8.1.10.5.1.1.4.1.1 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.12.5.1.1.4.1.1 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.13.5.1.1.4.1.1 INTEGER 0}
{1.3.6.1.4.1.2076.160.1.0.8.1.14.5.1.1.4.1.1 {OCTET STRING}
00:00:00:00:00:00}
{1.3.6.1.4.1.2076.160.1.0.8.1.15.5.1.1.4.1.1 INTEGER 0}
{1.3.6.1.4.1.2076.160.1.0.8.1.16.5.1.1.4.1.1 {OCTET STRING} {}}
{1.3.6.1.4.1.2076.160.1.0.8.1.17.5.1.1.4.1.1 INTEGER egrBlocked}
{1.3.6.1.4.1.2076.160.1.0.8.1.18.5.1.1.4.1.1 {OCTET STRING}
00:01:02:03:04:0A}
{1.3.6.1.4.1.2076.160.1.0.8.1.19.5.1.1.4.1.1 INTEGER 1}
{1.3.6.1.4.1.2076.160.1.0.8.1.20.5.1.1.4.1.1 {OCTET STRING}
53:6C:6F:74:30:2F:31:30}
{1.3.6.1.4.1.2076.160.1.0.8.1.21.5.1.1.4.1.1 {OCTET STRING} 1F:00:04:00:01}

ECFM
5.4 Configuring Y.1731 on Provider Backbone Bridges

This section describes the configuration of the Y.1731 functionality for provider backbone bridges on the
topology depicted in Figure 5-4.
Customer Network
(PCB)
Switch1
P1
Provider Backbone Network P10 BEB
(I-COMP)
Switch2
P9
P18
(B-COMP)
Switch3
P17
P26
Provider Backbone Network BEB
(B-COMP)
Switch4
P27 Bridge
P36 PCB Provider Core
(I-COMP) BEB
Switch5
Entity
P33 MIP
P42 Down MEP
Color code
(PCB) Level 7 VLAN 11
Switch6 Level 6 ISID 300
Figure 5-4: Configuration of Y1731 on Provider Backbone bridges

MAC address of ports on the bridges are of form 00:0m:02:03:04:0n, where m is bridge number and n is

Figure 5-4 depicts a topology for a provider backbone bridged network that consists of two customer
bridges (Switch1, Switch6), two I-component bridges (Switch2, Switch5), and two B-component bridges
(Switch3, Switch4). Switches 1 to 6 refer to six virtual contexts of the switch. Maintenance points
(MEP/MIP) are configured at same MD Level, and VLANs are shown using the same color code. Port P1,
P17, P26 and P42 are configured as PNP. P10 and P33 are configured as CNP. P9 is configured as PIP.
P18 is configured as CBP.
5.4.1 Enabling the Provider Backbone Bridging

• Enable provider backbone bridging

iss(config)# no shutdown provider-backbone-bridge
• Enable provider backbone bridging. [Index: None]

% snmp0 set {{fsPbbShutdownStatus.0 start}}
5.4.2 Configuring Default Bridge Mode and Interfaces
This section describes the configuration of default bridge mode and interfaces at virtual contexts.
At Switch1

ECFM
iss(config-if)# end
At Switch2
iss(config-if)# end
At Switch3


iss(config-if)# end
At Switch4
iss(config-if)# end
At Switch5

ECFM

iss(config-if)# end
At Switch6
iss(config-if)# end
At Switch1



At Switch2

ECFM

At Switch3



At Switch4

At Switch5

ECFM


At Switch6


5.4.3 Configuring Provider Bridge Mode
This section describes the configuration of provider bridge mode.
At Switch1
At Switch2
• Configure the bridge mode as provider backbone bridge (I-component)

ECFM

At Switch3
• Configure the bridge mode as provider backbone bridge (B-component)
At Switch4
• Configure the bridge mode as provider backbone bridge (B-component)
At Switch5
• Configure the bridge mode as provider backbone bridge (I-component)

At Switch6
At Switch1
At Switch2
• Configure the bridge mode as provider backbone bridge (I-component) [Index: ContextID = 2]

ECFM

At Switch3
• Configure the bridge mode as provider backbone bridge (B-component) [Index: ContextID = 3]
At Switch4
• Configure the bridge mode as provider backbone bridge (B-component) [Index: ContextID = 4]
At Switch5
• Configure the bridge mode as provider backbone bridge (I-component) [Index: ContextID = 5]

At Switch6
% snmp0 set {{fsDot1qGvrpStatus.6 disbaled}}
This section describes the initialization of the ECFM on all switches.
• Initialize ECFM on all the switches


ECFM


5.4.5 Configuring Interface Type
This section describes the configuration of the interface type.
At Switch1


iss(config-if)# end
• Configure port type of port P10 as CNP

iss(config-if)# end
At Switch2
At Switch3
iss(config-if)# end


ECFM
iss(config-if)# end
At Switch4
iss(config-if)# end

iss(config-if)# end
At Switch5
• Configure port type of port P33 as CNP s-tagged
iss(config-if)# end


iss(config-if)# end
At Switch6
iss(config-if)# end
At Switch1
At Switch2
• Configure port type of port P10 as CNP [Index: Interface number = 10]
At Switch3
At Switch4

ECFM
At Switch5
• Configure port type of port P33 as CNP s-tagged [Index: Interface number = 33]
At Switch6
5.4.6 Configuring VLAN and VLAN-mapping
This section describes the configuration of VLAN and VLAN mappings on respective switches.
At Switch1
At Switch2
• Create VLAN 11 and make interface P10 as member port
At Switch3


At Switch4
• Create BVLAN 10 and make P26 and P27 port as member port of this VLAN
At Switch5
At Switch6
At Switch1
• Create VLAN 11 and make interface P1 as member port of this VLAN [Index: ContextID =1, VLAN-ID=
11]


ECFM
At Switch2
[Index: ContextID =2, VLAN-ID= 11]

At Switch3



At Switch4
• Create BVLAN 10 and make ports P26 and P27 as member ports of this VLAN
[Index: ContextID = 4, VLAN-ID= 10]
snmp0 set {{fsDot1qVlanStaticRowStatus.4.10 createAndWait}}


[Index: ContextID = 4, VLAN-ID= 10]

At Switch5


At Switch6


5.4.7 Configuring Y.1731 and PBB
This section describes the configuration of Y.1731 and PBB on respective switches.
At Switch1
• Create down MEP of level 7 and VLAN 11 at interface P1

ECFM

Switch1
Switch Switch1
---------------------------------------------------------------------------
---------------------------------------------------------------------------
ma7 - Down 00:01:02:03:04:01 Active
At Switch2
iss(config-switch-si)#end
• Create down MEP of level 6 and service instance 300 at interface P9



iss(config-if)# ethernet cfm mep level 6 mpid 3 service-instance 300 active
iss# show ethernet cfm maintenance-point local mep interface gigabitethernet 0/9
Switch Switch2
-------------------------------------------------------------------------
-------------------------------------------------------------------------
ma6 300 Down 00:01:02:03:04:09 Active
At Switch3
• Configure service instance 300 and map port P18 to it. Also configure BVLAN mapping to map B-
VLAN 10 to ISID 300
• Create MIP of level 6 and service instance 300 at interface P18

iss(config-switch)# ethernet cfm default-domain service-instance 300 mip-creation-criteria
default level 6
iss(config-if)# ethernet cfm mip level 6 service-instance 300 active
iss(config-if)# end
iss# show ethernet cfm maintenance-point local switch Switch3
Switch Switch3
---------------------------------------------------------------------------

ECFM

---------------------------------------------------------------------------
- - 6 - MIP Gi0/18 -
- 300 - 00:01:02:03:04:12 Active
At Switch4
• Configure service instance 300 and map port P27 to it. Also map BVLAN 10 to ISID 300.

iss(config-switch)# ethernet cfm default-domain service-instance 300 mip-creation-criteria
default level 6
iss(config-if)# ethernet cfm mip level 6 service-instance 300 active
iss(config-if)# end
iss# show ethernet cfm maintenance-point local switch Switch4
Switch Switch4
---------------------------------------------------------------------------
---------------------------------------------------------------------------
- - 6 - MIP Gi0/27 -
- 300 - 00:01:02:03:04:1b Active
At Switch5

• Configure service instance 300 and map port P36 to it. Also configure SVLAN mapping to map S-
VLAN 11 to ISID 300 with untagged-pip as false
• Create down MEP of level 6 and service instance 300 at interface P36
iss# show ethernet cfm maintenance-point local mep interface gigabitethernet 0/36
Switch Switch5
------------------------------------------------------------------------
------------------------------------------------------------------------
ma6 300 Down 00:01:02:03:04:24 Active
At Switch6

ECFM

Switch6
Switch Switch6
---------------------------------------------------------------------------
---------------------------------------------------------------------------
ma7 - Down 00:01:02:03:04:2a Active
At Switch1
Create the maintenance domain [Index: ContextID =1, MD-Index = 1]

Create the maintenance association [Index: ContextID =1, MD-Index = 1, MA-Index = 1]






• Display MEP configuration at interface P1


{1.3.6.1.4.1.2076.160.1.0.4.1.3.1.1 {OCTET STRING} 6D:64:37}

{1.3.6.1.4.1.2076.160.1.0.4.1.4.1.1 INTEGER 7}
[Index: ContextID =1, MD-Index = 1, MA-Index = 1]


{1.3.6.1.4.1.2076.160.1.0.5.1.4.1.1.1 {OCTET STRING} 6D:61:37}


ECFM
{1.3.6.1.4.1.2076.160.1.0.5.1.2.1.1.1 INTEGER 11}

{1.3.6.1.4.1.2076.160.1.0.7.1.4.1.1.1.1 Unsigned32 0}

{1.3.6.1.4.1.2076.160.1.0.7.1.2.1.1.1.1 INTEGER 1}

{1.3.6.1.4.1.2076.160.1.0.7.1.3.1.1.1.1 INTEGER down}

{1.3.6.1.4.1.2076.160.1.0.7.1.5.1.1.1.1 INTEGER true}
At Switch2

% snmp0 set {{fsPbbVipToPipMappingRowStatus.2.5255 createAndWait }}
% snmp0 set {{fsPbbVipToPipMappingRowStatus.2.5255 active}}


• Create down MEP of level 6 and ISID 300 at interface P9

Create the maintenance association [Index: ContextID =2, MD-Index = 1, MA-Index = 1,

fsMIEcfmExtMaPrimarySelectorType =2, ISID = 300]
% snmp0 set {{fsMIEcfmExtMaFormat.2.1.1.2.300 charString }}
% snmp0 set {{fsMIEcfmExtMaCcmInterval.2.1.1.2.300 interval1s }}
Configure MEP list



At Switch3
• Configure service instance 300 and map port P18 to it. Also configure BVLAN mapping to map B-Vlan
10 to ISID 300
[Index: ContextID =3, Interface number = 18, ISID = 300]

ECFM






[Index: ContextID = 3, Service selector = 2, ISID = 300]
% snmp0 set {{fsMIEcfmExtDefaultMdMhfCreation.3.2.300 defMHFdefault}}
% snmp0 set {{fsMIEcfmExtDefaultMdLevel.3.2.300 6}}
[Index: Interface number = 18, MD-Level = 6, Service selector = 2, ISID = 300]

% snmp0 set {{fsMIEcfmExtMipRowStatus.18.6.2.300 createAndWait}}
% snmp0 set {{fsMIEcfmExtMipRowStatus.18.6.2.300 active}}
At Switch4
• Configure service instance 300 and map port P27 to it. Also map BVLAN 10 to ISID 300 [Index:
ContextID = 4, Interface number = 27, ISID = 300]

[Index: ContextID = 4, Service selector = 2, ISID = 300]
% snmp0 set {{fsMIEcfmExtDefaultMdMhfCreation.4.2.300 defMHFdefault}}
% snmp0 set {{fsMIEcfmExtDefaultMdLevel.4.2.300 6}}

[Index: Interface number = 27, MD-Level = 6, Service selector = 2, ISID = 300]

% snmp0 set {{fsMIEcfmExtMipRowStatus.27.6.2.300 createAndWait}}
% snmp0 set {{fsMIEcfmExtMipRowStatus.27.6.2.300 active}}
At Switch5
• Configure service instance 300 and map port P36 to it. Also, configure SVLAN mapping to map S-
VLAN 11 to ISID 300 with untagged-pip as false
% snmp0 set {{ifMainRowStatus.5256 createAndWait }}


• Create down MEP of level 6 and ISID 300 at interface P36


ECFM
Create the maintenance association [Index: ContextID = 5, MD-Index = 1, MA-Index = 1,

fsMIEcfmExtMaPrimarySelectorType =2, ISID = 300]
% snmp0 set {{fsMIEcfmExtMaFormat.5.1.1.2.300 charString}}
% snmp0 set {{fsMIEcfmExtMaCcmInterval.5.1.1.2.300 interval1s}}
Configure MEP list


Configure the MEP [Index: ContextID = 5, MD-Index = 1, MA-Index = 1, MEP-ID = 2]

At Switch6
Create the maintenance association [Index: ContextID =6, MD-Index = 1, MA-Index = 1]



Configure MEP list


Configure MEP [Index: ContextID =6, MD-Index = 1, MA-Index = 1, MEP-ID = 2]

% snmp0 set {{fsMIEcfmMepDirection.6.1.1.2 1}}
% snmp0 set {{fsMIEcfmMepActive.6.1.1.2 1}}

{1.3.6.1.4.1.2076.160.1.0.4.1.3.6.1 {OCTET STRING} 6D:64:37}
{1.3.6.1.4.1.2076.160.1.0.4.1.4.6.1 INTEGER 7}
[Index: ContextID =6, MD-Index = 1, MA-Index = 1]

{1.3.6.1.4.1.2076.160.1.0.5.1.4.6.1.1 {OCTET STRING} 6D:61:37}

ECFM

{1.3.6.1.4.1.2076.160.1.0.5.1.2.6.1.1 INTEGER 11}

{1.3.6.1.4.1.2076.160.1.0.7.1.4.6.1.1.2 Unsigned32 0}
{1.3.6.1.4.1.2076.160.1.0.7.1.2.6.1.1.2 INTEGER 42}
{1.3.6.1.4.1.2076.160.1.0.7.1.3.6.1.1.2 INTEGER down}
{1.3.6.1.4.1.2076.160.1.0.7.1.5.6.1.1.2 INTEGER true}
5.4.8 Enabling Y.1731 on all Switches
This section describes the enabling of the Y.1731 feature on all the switches.
• Enable Y1731 status



• Enable Y1731 status

5.4.9 Detecting Fault
This section describes the enabling of CC for detecting fault.



ECFM





5.4.10 Check for Continuity Defects
This section describes the verification of link failures using continuity defects/errors

• Wait for 15 seconds after doing the configurations explained upto section 5.4.9.1 and then check for
any defect/fault
Switch default
Switch Switch1
Switch Switch2
Switch Switch3
Switch Switch4
Switch Switch5
Switch Switch6
iss#
Shows no link failure, as no error is detected at any of the switches.
• Wait for 15 seconds after doing the configurations explained upto section 5.4.9.2 and then check for
any defect/fault
{1.3.6.1.4.1.29601.2.13.1.2.3.1.14.1.1.1.1 {OCTET STRING} 00}

{1.3.6.1.4.1.29601.2.13.1.2.3.1.14.6.1.1.2 {OCTET STRING} 00}
Shows no link failure, as no error is detected at any of the switches.
5.4.11 Configuring and Enabling AIS

This section describes configuration and enabling of the transmission of AIS PDU by an MEP.

ECFM
• Configure client layer level.

iss(config-ether-ecfm)# client-layer-level 7
• 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.
• Configure client layer level MEP [Index: ContextID = 2, MD-Index = 1].

• 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. [Index: ContextID = 2, MD-Index = 1, MA-
5.4.12 Configuring and Enabling LCK
This section describes configuration and enabling of the transmission of LCK PDU by an MEP.
Client MEG must be set for the maintainance domain of the MEP before setiing the
MEP as out-of-service.

• Enable LCK capability on the MEP, so that when any defect occurs, the MEP starts transmitting the
LCK to all the MEP(s) configured at the client layer level.
• Enable MEP to perform out-of-service operations. [Index: ContextID = 2, MD-Index = 1, MA-Index = 1,

MEP-ID = 1].
5.4.13 Verifying One-Way Connectivity Using TST
This section describes the configuration and enabling of the transmission and reception of TST PDU by an
MEP.
• Send the TST message to an MEP using.MEPID

iss# ethernet cfm test mpid 4 level 6 service-instance 300 switch Switch2
TST to 4 from 00:01:02:03:04:09 with 33(64) bytes of data.
60 bytes to 00:01:02:03:04:24: seq_no=0
60 bytes to 00:01:02:03:04:24: seq_no=1
60 bytes to 00:01:02:03:04:24: seq_no=2
60 bytes to 00:01:02:03:04:24: seq_no=3
60 bytes to 00:01:02:03:04:24: seq_no=4
60 bytes to 00:01:02:03:04:24: seq_no=5
60 bytes to 00:01:02:03:04:24: seq_no=6
60 bytes to 00:01:02:03:04:24: seq_no=7
60 bytes to 00:01:02:03:04:24: seq_no=8
60 bytes to 00:01:02:03:04:24: seq_no=9
60 bytes to 00:01:02:03:04:24: seq_no=10
--- 4 test statistics ---

ECFM
• Send the TST message to an MEP using.MEPID [Index: ContextID = 2, MD-Index = 1, MA-Index = 1,
MEP-ID = 1]
• Verify whether test messages are transmitted and received successfully.

{1.3.6.1.4.1.29601.2.7.1.2.4.1.58.2.1.1.1 Unsigned32 89}

% snmp0 get {fsMIY1731MepValidTstIn.5.1.1.2}
{1.3.6.1.4.1.29601.2.7.1.2.4.1.57.5.1.1.2 Unsigned32 89}
5.4.14 Monitoring Performance
This section describes the monitoring of the performance by an MEP.
5.4.14.1 Configuring Frame Delay Measurement
This section describes the steps to configure and enable the transmission and reception of Frame delay
PDU by an MEP.
Frame delay can be measured using either of the following methods:
1. One-way Frame Delay Measurement
2. Two-way Frame Delay Measurement
5.4.14.1.1 CLI Configurations
• Send the One-way frame delay message to an MEP.

iss# ethernet cfm frame delay start type one-way level 6 service-instance 300 mpid 4 switch
Switch2
• Send the Two-way frame delay message to an MEP.

iss# ethernet cfm frame delay start type two-way level 6 service-instance 300 mpid 4 switch
Switch2
• User can stop the frame delay measurement by either:

• configuring the count or deadline parameter while initiating the delay measurement.
OR
• using the ethernet cfm frame delay stop type level service-instance command.
5.4.14.1.2 SNMP Configurations
• Send the One-way frame delay message to an MEP [Index: ContextID = 2, MD-Index = 1, MA-Index =
1, MEP-ID = 1].
% snmp0 set {{fsMIY1731MepTransmitDmType.2.1.1.1 oneWay}}
• Send the Two-way frame delay message to an MEP [Index: ContextID = 2, MD-Index = 1, MA-Index =
1, MEP-ID = 1].

• Configuring the number of messages or deadline parameter while initiating the delay
measurement. [Index: ContextID = 2, MD-Index = 1, MA-Index = 1, MEP-Index = 1]
% snmp0 set {{fsMIY1731MepTransmitDmDeadline.2.1.1.1 10}}
OR
• Configuring the transmit status as stop [Index: ContextID = 2, MD-Index = 1, MA-Index = 1,
MEP-Index = 1].
% snmp0 set {{fsMIY1731MepTransmitDmStatus.2.1.1.1 stop}}
5.4.14.2 Configuring Frame Loss Measurement
This section describes the steps to configure and enable the transmission and reception of frame loss
PDU by an MEP.
Frame loss can be measured using either one of the following methods:
1. Dual-ended using CCM messages
2. Single-ended using LMM/LMR messages

ECFM
• Single-ended frame loss

• Send the message to an MEP using destination MPID.
iss# ethernet cfm frame loss start level 6 service-instance 300 mpid 4 switch Switch2
• User can stop the frame loss measurement by either
• configuring the count or deadline parameter while initiating the loss measurement,
OR
• using the ethernet cfm frame loss stop level vlan command.
• Dual-ended frame loss

• Configure the CC unicast MAC address. This is the MAC address of the remote MEP with which the
frame loss is to be measured.
iss(config-ether-mep)# set ccm- mac unicast 00:02:02:03:04:03
iss(config-switch)# ethernet cfm cc level 6 service-instance 300 role performance-monitoring
iss(config)# end
• Stop dual-ended frame loss measurement either by

• Disabling CC transmission
iss(config-switch)# no ethernet cfm cc enable level 6 service-instance 300
iss(config)# end
OR
• Changing the CC role to role other than performance monitoring
iss(config-switch)# ethernet cfm cc level 6 service-instance 300 role fault-management
iss(config)# end

• Single-ended frame loss

• Send the message to an MEP using destination MAC address [Index: ContextID = 2, MD-Index = 1,
MA-Index = 1, MEP-ID = 1].
• Stop the frame loss measurement [Index: ContextID = 2, MD-Index = 1, MA-Index = 1, MEP-ID = 1]
% snmp0 set {{fsMIY1731MepTransmitLmmStatus.2.1.1.1 stop}}
• Send the message to measure frame loss by setting the role as performance-monitoring [Index:
% snmp0 set {{fsMIY1731MeCcmApplication.2.1.1 ccPerformanceMonitoring}}
• Stop dual-ended frame loss measurement by setting role other than performance-monitoring [Index:
% snmp0 set {{fsMIY1731MeCcmApplication.2.1.1 ccFaultManagement}}
5.4.14.3 Configuring Throughput Measurement
This section describes the steps to configure and enable the throughput measurement at an MEP.
Throughput can be measured using one of the following methods:
1. One-way Throughput Measurement
2. Two-way Throughput Measurement
• Start the one-way throughput measurement at an MEP using destination MPID.

iss# ethernet cfm throughput type one-way mpid 4 level 6 service-instance 300 switch Switch2
--- 4 one-way throughput statistics ---
final throughput 1197599 bps / 1.197599 mbps, packet size 1496 bytes

ECFM
• Start the two-way throughput measurement at an MEP using destination MPID.

iss# ethernet cfm throughput type two-way mpid 4 level 6 service-instance 300 switch Switch2
--- 4 two-way throughput statistics ---
final throughput 1197599 bps / 1.197599 mbps, packet size 1496 bytes
The above mentioned steps are only for initiating the throughput transaction. The
user may not get the same output. To get the same output, target entity also needs to
be configured.
• Start the one-way throughput measurement at an MEP using destination MAC address. [Index:
ContextID = 2, MD-Index = 1, MA-Index = 1, MEP-ID = 1].
% snmp0 set {{fsMIY1731MepTransmitThDestMacAddress.2.1.1.1 00:01:02:03:04:24}}
% snmp0 set {{fsMIY1731MepTransmitThPps.2.1.1.1 100}}

% snmp0 set {{fsMIY1731MepTransmitThBurstDeadline.2.1.1.1 5000}}
% snmp0 set {{fsMIY1731MepTransmitThType.2.1.1.1 oneWay}}
% snmp0 set {{fsMIY1731MepTransmitThFrameSize.2.1.1.1 512}}
% snmp0 set {{fsMIY1731MepTransmitThStatus.2.1.1.1 active}}
• Start the two-way throughput measurement at an MEP using destination MAC address. [Index:
ContextID = 2, MD-Index = 1, MA-Index = 1, MEP-ID = 1].
% snmp0 set {{fsMIY1731MepTransmitThDestMacAddress.2.1.1.1 00:01:02:03:04:24}}
% snmp0 set {{fsMIY1731MepTransmitThPps.2.1.1.1 100}}

% snmp0 set {{fsMIY1731MepTransmitThBurstDeadline.2.1.1.1 5000}}
% snmp0 set {{fsMIY1731MepTransmitThType.2.1.1.1 twoWay}}
% snmp0 set {{fsMIY1731MepTransmitThFrameSize.2.1.1.1 512}}
% snmp0 set {{fsMIY1731MepTransmitThStatus.2.1.1.1 active}}

Your Opinion Matters
Dear Reader:
We aspire to provide you with important information, delivered efficiently. If this guide has been
informative, useful, and effective, your satisfaction is our reward. If not, tell us how it can be improved.
Your valuable input will help us understand your information needs better.
Please fill up the form provided below and mail it to us at the address provided on the Copyright page.
Did you find the INFORMATION provided in this guide:

Complete Y N Accurate Y N
Relevant Y N Well-organised Y N
Other:
Did you find the LANGUAGE used in this guide:

Easy to understand Y N Correct Y N
Consistent Y N Professional Y N
Other:
Did you find the TONE used in the delivery:

Appropriate Y N Professional Y N
Other:
Did you find the ILLUSTRATIONS provided in the guide:

Relevant Y N Easy to understand Y N
Other:
Did you find the PAGE LAYOUT:

Aesthetically pleasing Y N Crowded Y N
Other:
What improvements do you recommend for this document?

____________________________________________________
____________________________________________________
____________________________________________________
Document No. ARICENT: ECFMConfigum/20090603
Thank you for participating in our quest for total customer satisfaction.

Revision History
ECFM Revision Number: 11.0

Configuration User Manual ARICENT: ECFMConfigum/20090603
01-06-2009
Path:


ECFMConfigUM PDF

Uploaded by

Copyright:

Available Formats

ECFMConfigUM PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ECFMConfigUM PDF

Uploaded by

Copyright:

Available Formats

ECFM aricent.

Revision Number: 11.0

CHAPTER 1: 1. INTRODUCTION _____________________________________________ 13

CONFIGURATION USER MANUAL 1

3.3.3.2 SNMP Configurations ------------------------------------------------------------ 36

3.3.21 Setting OUI (Organizational Unit Identifier)........................................... 69

CONFIGURATION USER MANUAL 3

5.1.1.1 CLI Configurations ---------------------------------------------------------------- 95

5.2.1.2 SNMP Configurations ---------------------------------------------------------- 121

CONFIGURATION USER MANUAL 5

5.3.5 Configuring Interface Type.................................................................. 190

5.4.14.1 Configuring Frame Delay Measurement----------------------------------- 260

CONFIGURATION USER MANUAL 7

Figure 2-1 Maintenance Domain in ECFM.................................................................................................. 24

CONFIGURATION USER MANUAL 9

Table 1-1: Acronyms Used in this Document.............................................................................................. 13

CONFIGURATION USER MANUAL 11

1.1 Purpose and Scope

1.2 Acronyms and Abbreviations

Table 1-1: Acronyms Used in this Document

CONFIGURATION USER MANUAL 13

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

Table 1-2: Terminology Mapping

Maintenance Entity Group (MEG) Maintenance Domain (MD)

Maintenance Entity Group Intermediate Maintenance Domain Intermediate Point (MIP)

CONFIGURATION USER MANUAL 15

1.5 Document Conventions

Guidelines / Pre-requisites are keyed inside this text box

Output areas specific to the configuration

 These topics convey additional information on an associated topic.

1.6 General Configurations

1.6.1 CLI Configurations

Command Mode Access Method Prompt Exit method

1.6.2 SNMP Configurations

1.6.2.1 SNMP Operations

1.6.2.1.1 MIB Load

Syntax: mib load mib_file.mib

CONFIGURATION USER MANUAL 17

MIB Name Object prefix Description

1.6.2.1.2 Set Operation

1.6.2.1.3 Get Operation

CONFIGURATION USER MANUAL 19

{1.3.6.1.4.1.2076.138.1.1.1.2.1 INTEGER providerBackoneICompBridge}

1.6.2.1.4 Walk Operation

1.6.2.2 Interface Range

Table 1-6: Interface Index Range

Table 1-7: Scalability Constants

CONFIGURATION USER MANUAL 21

2.1 Ethernet CFM

CONFIGURATION USER MANUAL 23

CFM Functions are categorized as follows:

2.2 Maintenance Domain

Figure 2-1 Maintenance Domain in ECFM

2.3 Maintenance Association / Service Instance

Figure 2-2 Maintenance Association

Figure 2-3 Example Maintenance Association

CONFIGURATION USER MANUAL 25

2.4 Maintenance Point

Figure 2-4 Maintenance Point in ECFM

These topics convey additional information on an associated topic.

AIS frame can be multicast or unicast.

LCK frame can be multicast or unicast.

TST frame can be multicast or unicast.

The MD must be configured prior to the configuration of MA.

The MD and MA must be configured prior to the configuration of the MEP.