ECFM System Test Plan

<AM3100> aricent.
com
ECFM System Test Plan
ARICENT:
Revision Number:
Copyright © 2007 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, 3460 Hillview Avenue, Palo Alto, CA 94304.
DOCUMENT No.: ARICENT:

Contents
CHAPTER 1: 1. INTRODUCTION________________________________________________7
1.1 PURPOSE.................................................................................................... 7
1.2 SCOPE........................................................................................................ 7
1.3 DEFINITIONS AND ACRONYMS.......................................................................8
1.4 REFERENCES..............................................................................................8
CHAPTER 2: 2. TEST PLAN___________________________________________________11
2.1 OBJECTIVE OF TEST..................................................................................11
2.2 TEST METHOD...........................................................................................11
2.3 ENTRY AND EXIT CRITERIA FOR SYSTEM TESTING......................................13
2.3.1 Entry Criteria......................................................................................... 13
2.3.2 Exit Criteria........................................................................................... 13
2.4 TEST SCHEDULE.......................................................................................13
2.5 FAULT REPORTING AND MONITORING PROGRESS.......................................13
2.6 BUILD PLAN AND BUILD REFRESH CRITERIA...............................................13
2.7 RESOURCE REQUIREMENTS.......................................................................14
2.7.1 Hardware Requirements.......................................................................14
2.7.2 Software Requirements........................................................................14
CHAPTER 3: TOPOLOGIES___________________________________________________17
2.8 - SETUP 1................................................................................................. 17
2.9 – SETUP 2................................................................................................ 18
2.10 - TEST CONFIGURATIONS..........................................................................19
CHAPTER 4: 3. TEST CASES_________________________________________________23
3.1 – CONFIGURATION TESTCASES..................................................................23
3.2 CONTINUITY CHECK MESSAGES – CCM.....................................................44
Revision History_________________________________________________76
ECFM SYSTEM TEST PLAN 1

ARICENT CONFIDENTIAL
Figures
Figure 0-1: TEST SETUP 1........................................................................................................................ 18

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

Table 2-1: Hardware Requirements............................................................................................................ 14
Table 2-2: Software Requirements............................................................................................................. 14
Chapter
1
1.Introduction
1.1 Purpose
The purpose of this document is to describe the various test cases, testing
methodologies, environments and the software/hardware tools that would be
used/followed during System testing in the project.
1.2 Scope
System testing is to be performed on AM3100 by using topologies inclusive
of 2 to 3 devices.
Scope:
 The system is tested as a whole from the perspective of the users

who interact with system via external interfaces.
 The testing would be conducted on a target platform similar to the

customer setup against a formal testplan.
 The main aim of the testing would be to capture all the defects during
this testing phase.
 The testing phase will stop until all testcases are executed and all
critical/major defects are fixed.
1.3 Definitions and Acronyms
Table Introduction-1: Acronyms Used in this Document

Acronym Explanation
DA Deliverable Audit
FW Firmware
GE Gigabit-Ethernet
GPON Gigabit Passive Optical Network
GUI Graphical User Interface
IGMP Internet Group Management Protocol
IGU Integrated Gateway Unit
ISS Intelligent Switch Solution
ITU-T International Telecommunication Union – Telecommunication
Standardization Sector
MRS Marketing Requirement Spec
NE Network Element
NECA NEC Australia
OLT Optical Line Termination
ONT Optical Network Terminal
ONU Optical Network Unit
PO Purchase Order
PTP Point-to-Point
RSTP Rapid Spanning Tree Protocol
SoW Scope of Work
VLAN Virtual VLAN
CFM Connectivity Fault Management
MEP Maintenance End Point
MIP Maintenance Intermediate Point
LBM Loopback message
LTM Linktrace message
CCM Continuity Check Message.
1.4 References
1. NEC-A outsourcing proposal –SOW from Aricent.

2. NE Outsource Requirements_SR4 10_Issue 2 document - Outlining the
firmware outsourcing requirements for system Release 4.10 shared on
Nov 23, 2009
3. TR-101 – Technical Report from DSL Forum for Migration to Ethernet-Based
DSL Aggregation”
4. System Test Plan Guidelines
Chapter
2
2.Test Plan
2.1 Objective of Test
The objective of the system test is to test the functionality, stability, scalability
and performance of the system and to ensure that the software conforms to
requirements stated in SRS and meets the customer acceptance criteria.
2.2 Test Method
Functionality Testing
Following test cases are executed to check for the various functionalities as
detailed in SRS
<Specify the Ids of test cases that check the functionality of the system>
Performance Testing
Following test cases are executed to check for the performance of the
system as detailed in SRS
<Specify the Ids of test cases that check performance of the system>

Load/Stress Testing
Following test cases are executed to check the maximum load the software
can withstand
<Specify the Ids of test cases that check the maximum load system can
withstand, out-of-boundary and invalid input conditions, high volume and
peak load simulations, operational errors etc. >
Scalability Testing
Following test cases are executed to check the scalability of the software
<Specify the Ids of test cases that check to scalability of the system>
Negative Testing
Following test are the negative test cases
<Specify the Ids of negative test cases to check hardware errors, software
errors, overload traffic, Invalid user input, system recovery from an outage
etc.
Other test cases
<Specify here id s of any other special tests that are carried out>
Test Tools
Ixia Traffic Generator/Analyzer.
Test Scripts
<Specify test scripts that will be used for testing here, and location in the
project folder where it will be stored >
RT Coverage Tool
<Specify the testing tool used to measure coverage >

CHAPTER 0: TOPOLOGIES
2.3 Entry and Exit Criteria for System Testing
2.3.1 Entry Criteria
 Unit testing and integration testing complete

 Approved Release test plan
2.3.2 Exit Criteria
 System testing complete.

 System Test records produced.
 Fault records produced and resolved.
 RT Coverage record (if applicable)
 All acceptance criteria’s as specified by customer are met
2.4 Test Schedule
As defined in the project plan.
2.5 Fault Reporting and Monitoring Progress
 Fault reports are maintained. Fault records can also be maintained in the
test automation tool (by CHN)
 The Project manager will issue a test progress report to the team
members and to the Engineering Manager on a defined frequency
(recommended weekly). If test record automation tool is used, test status
is available online.
2.6 Build Plan and Build Refresh Criteria
A new build of the software is made whenever

 A fault is found which prevents further testing

<AM3100>
 All test cases have been executed and some faults have been corrected
2.7 Resource Requirements
2.7.1 Hardware Requirements
Table Test Plan-2: Hardware Requirements
Resource Quantity Descripti

on
IGU-8E1000 2 IGU cards
IGU-2E10G 2 IGU cards
IGU-8E1000-2 2 IGU cards
Ixia ports 2 Traffic
generator/an
alyzer ports.
Linux PC 2 To load ISS
simulator
Windows PC 2 For VLC
Server/Clien
t, testing
multicast
SFP – 1Gig 5 Small Form
Pluggable
capable of 1
Gig
Cables 15 For
interconnecti
ng devices
L2-Switch 1 Used while
testing
ASLP
Chassis AM3100 2 For system
testing
2.7.2 Software Requirements
Table Test Plan-3: Software Requirements
14 ARICENT:
Software Description Qty

SNMP Manager To test via SNMP 1

Chapter
3
Topologies
2.8 - Setup 1
NET
SNMP
Mgr
FE/GE
AM 3100 IGU Port 0/3
ISS
Simulat
or
IGU Port 0/2
FE/GE
IGU Port 0/1
IXIA
FE/GE FE/GE
Port 1 Port 2

Figure Figure Figure Figure Figure Figure -1: TEST SETUP 1-1: TEST SETUP 1-1:
TEST SETUP 1-1: TEST SETUP 1-1: TEST SETUP 1-1: TEST SETUP 1
2.9 – Setup 2
NET
SNMP
Mgr
FE/GE
AM 3100 IGU Port 0/5 AM 3100
IGU Port 0/2 & 3

ISS
Simulat
IGU Port 0/1 or
FE/GE
IGU Port 0/4 FE/GE

IGU Port 0/1
IXIA
FE/GE Port 1 Port 2 FE/GE

Figure Figure Figure Figure Figure Figure -2: TEST SETUP 2-2: TEST SETUP 2-2:
TEST SETUP 2-2: TEST SETUP 2-2: TEST SETUP 2-2: TEST SETUP 2
2.10 - Test Configurations

S/no CLI Description Functional Description
1 iss> enable
Password: admin123 Interface Configuration
iss# configure terminal
iss(config)#
iss(config)# interface gigabitethernet 0/1
iss(config-if)# no shutdown
iss(config-if)# map switch default
iss(config-if)# end
iss(config)# switch cust
iss (config-switch)# bridge-mode customer
iss (config-switch)# end
2 iss(config)# vlan 2 Vlan Configuration
iss(config-vlan)# ports gigabitethernet 0/1-3
untagged gigabitethernet 0/1
iss(config-vlan)# exit
3 iss# write startup-config For save and Restore

4 iss# show vlan [brief, id(vlan), summary] For retrieving vlan information.
iss# show service-vlan
5 iss# show vlan counters For retrieving statistics
iss# show vlan statistics
iss# show interfaces
iss# show interfaces - counters
6 Iss# show mac-address-table For retrieving mac entries from the FDB
table.
7 iss# set port-channel {enable | disable} For configuring etherchannel and retrieve the
iss(config-if)# channel-group 1 mode active information.
iss# show etherchannel
iss# show interfaces gigabitethernet 0/1
etherchannel
8 Iss(config-if)#switchport service vlan mapping S-vlan translation
<local service vlan integer(1-4094)> <relay
service vlan integer(1-4094)>
9 Iss(config-if)#service-vlan <vlan-id (1-4094)> 1:1 s-vlan configuration.
pvid <vlan-id(1-4094)>
Iss(config-if)#service-vlan <vlan-id (1-4094)>
acceptable-frame-type all
Iss#show service-vlan
10 Iss(config)#bridge-mode {customer | Service vlan should be configured unless the
provider-edge | provider-edge-edge | bridge-mode is set to provider-edge.
provider-edge-core}
Iss# show bridge-mode
11 Iss(config)# ethernet cfm enable Enabling and Disabling ECFM at the global

<AM3100>
Iss(config)# no ethernet cfm enable level.

12 iss(config)# ethernet cfm domain name Maintenance Domain creation and deletion
TestDomain1 level 7 on bridge.
iss(config)# no ethernet cfm domain name
TestDomain1 level 7
13 iss(config-ether-ecfm)# service name Maintenance Association creation and
CustAssoc1 vlan 101 deletion on bridge.
iss(config-ether-ecfm)#no service name
CustAssoc1
14 iss(configure-if)#ethernet cfm mep level 7 Maintenance Point Configuration
mpid 5 vlan 101 − Maintenance Association End Point (eight
iss(config-if)#no ethernet cfm mep level 7 Up MEPs and eight Down MEPs)
mpid 5 vlan 101 configuration on each Port per VLAN per MD
Level on Bridge is supported at different MD
iss(config-if)#ethernet cfm mip level 7 vlan levels.
101 − Maintenance Association End Points
(eight Down MEPs) configuration on each
Port attached to no VLAN or ISID on Bridge
is supported at different MD levels.
− Maintenance Association Intermediate
Points configuration on each Port (at highest
MD Level) all MIPs being at same MD Level.
− Configuration of MEPs and MIPs
associated with VLANs or ISIDs on Logically
Aggregated ports.
15 iss(config)# ethernet cfm cc level 1 vlan 101 Connectivity Check Mechanism
interval ten-ms − Configurability of periodicity of the CCMs.
iss(config)# ethernet cfm cc enable level 1 − Management of MEP CCM Database.
vlan 101
16 iss# ping ethernet mac 00:02:02:03:04:03 Loop Back Mechanism
level 7 vlan 101 count 1 − Initiation of LBM by MEPs only
17 iss# traceroute ethernet mac Link Trace Mechanism
00:02:02:03:04:02 level 7 vlan 101 time-to- − Initiation of LTM messages by MEPs only
live 32
18 iss# show ethernet cfm domain brief Displaying the maintenance domain
information. This include MD name, index,
level, etc.
19 iss# show ethernet cfm service brief Displaying the maintenance association
information. The information includes MA
name, domain name, level, primary vlan, etc.
20 iss# show ethernet cfm maintenance-point Displaying maintenance point configured.
local mep
21 To associate a set of vlans to the primary

iss(config)#ethernet cfm associate vlan-id vlan-id.
1,2,3 primary-vlan-id 7
22 iss(config)# ethernet cfm mip dynamic For dynamic mip creation.
evaluation
23 iss(config)# ethernet cfm cc level 1 vlan 101 To configure Continuity Check messages.
interval ten-ms
iss(config)# ethernet cfm cc enable level 1
vlan 101
20 ARICENT:
iss(config)# no ethernet cfm cc enable level 1

vlan 101
24 iss(config-if)#ethernet cfm llc-encap enable For enabling/disabling llc-encap.
iss(config-if)#ethernet cfm llc-encap disable
25 ping ethernet mac <Mep-id-mac-address> For initiating loopback messages
level <no> vlan <id> count <no>
26 iss#config terminal For initiating Linktrace messages
iss(config)#ethernet cfm traceroute cache
iss(config)#end
iss# traceroute ethernet mac <interface mac

address> level <id> vlan <id>

Chapter
4
3.Test Cases
3.1 – Configuration Testcases

Test Case Id
ECFM_SYS_FN_ 1
Test Description To check whether CFM should be enabled/disabled globally.

Test Topology 2.8
Test Pre-
AM3100 should be up and running.
requisite
Test Procedure
# Test Input Expected Test Output
1 Enable CFM globally for the bridge. This should be ECFM should be globally configured
configured by using the below command: for the bridge.
CLI command: 2.10-11 CLI command: 2.10-11
2 Disable CFM globally for the bridge. This should be ECFM should be globally disabled
configured by using the below command: for the bridge.
Test Case Id ECFM_SYS_FN_ 2
Test Description 1. To check creation of Maintenance Domain at a particular level.

2. To check that Multiple Maintenance Domain should be created at the same

level.
3. To check that MD Names are unique in the system (bridge).
4. To check that domain deletion is supported.
Test Topology 2.8
Dependency 1) AM3100 should be up and running.
2) ECFM_SYS_FN_1 should pass.
3) Bridge-mode should be set to Provider-edge
Test Procedure
1 Create Maintenance Domain The maintenance domain should be
MdName = OP1, MdLevel = 1 successfully created. This should
be retrieved by using the below cli
CLI command: 2.10-12
command: 2.10-18
MdName = OP2, Domain Level = 1 successfully created. This should
command: 2.10-18
successfully created. This should be
MdName = OP3, MdLevel = 2
retrieved by using the below cli
CLI command: 2.10-12 command: 2.10-18
4 Create Maintenance Domain The maintenance domain creation
would fail. This should be verified by
using the below cli command: 2.10-
CLI command: 2.10-12 18
5 Create Maintenance Domain Verify that MD with MdName OP3 at
level 3 is not created since domain
with the same name already exists.
6 Delete the above configured Maintenance domains. The maintenance domains should be
CLI command: 2.10-12 successfully deleted.
Cli command: 2.10-18
Test Description To check that only a valid level-id i.e. between 0 - 7 is allowed when creating
MD.
Test Topology 2.8
Test Pre- 1) AM3100 should be up and running.
requisite 2) ECFM_SYS_FN_1 should pass.
Test Procedure
1 Create Maintenance Domain Verify that MD with MdName
MdName = Customer1, MdLevel = -2 Customer1 at level -1 is not

REVISION HISTORY
CLI command: 2.10-12 created.

2 Create Maintenance Domain Verify that MD with MdName
MdName = Customer1, MdLevel = 8 Customer1 at level 8 is not created.
3 Create Maintenance Domain Verify that MDs with MdName
MdName = Customer0, MdLevel = 0 Operator0 at Level 0 and
Customer2 at Level 2 are created.
Test Description To test that deletion of the Maintenance Domain at the specified level is allowed
only when it has no Maintenance Association associated with it.
Test Topology 2.8
Test Procedure
CLI command: 2.10-12 be retrieved by using the below cli
command: 2.10-18
2 Create Maintenance Association for MD = OP1 at level 1 The maintenance association can
with be successfully configured for the
MaName = maoper1, PrimaryVlanId = 2 MD.
CLI command: 2.10-13 Cli command: 2.10-18
3 Delete Maintenance Domain MD = OP1 As MA is associated with MD, MD
CLI command: 2.10-12 cannot be deleted.
cli command: 2.10-18
4 Delete MA maoper1 Verify that MA should be deleted.
5 Delete Maintenance Domain MD = OP1 Verify that the MD should be deleted.
CLI command: 2.10-12 cli command: 2.10-18
Test Description 1. To check the creation of Maintenance association for a particular VLAN for a
particular MD level is successful
2. To check that MA is created only when MD for which it is to be created exist.
3. To check that MA is not created if there is already a MA configured in the
Maintenance Domain with the same MA name.
Test Topology 2.8
<AM3100>

Test Procedure
1 Create Maintenance Association for MD = oper6 at level 6 Verify that there is no MA created
with because the MD for which MA is to
MaName = maoper6, PrimaryVlanId = 2 be created does not exist.
MdName = oper6, MdLevel = 6 successfully created. This should be
CLI command: 2.10-12 retrieved by using the below cli
command: 2.10-18
3 . Create Maintenance Association for MD = oper6 at level Verify that MA maoper6 is created in
6 with MaName = maoper6, PrimaryVlanId = 2 domain oper6 at level 6 and
CLI command: 2.10-13 PrimaryVlanId 2.
4 Create Maintenance Association for MD = oper6 at level 6 Verify that MA maoper6 is not
with created in domain oper6 at level 6
MaName = maoper6, PrimaryVlanId = 7 and PrimaryVlanId 7 since there is
CLI command: 2.10-12 already exist an MA with same
name.
Test Description 1. To test for creation of MA that is associated with more than one VLAN is
successful.
2. To test that a primary VID can be associated with more than one MA at a
particular MD level.
Test Topology 2.8
Test Procedure
MdName = oper5 MdLevel = 5 successfully created. This should
Create Maintenance Domain command: 2.10-18
MdName = oper6 MdLevel = 6
2 Create Maintenance Association for MD = oper5 at level Verify that MA maoper5 is created.
5 with
MaName = maoper5, PrimaryVlanId = 10 Cli command: 2.10-19
5 with Cli command: 2.10-19
26 ARICENT:
REVISION HISTORY
MaName = maoper6, PrimaryVlanId = 101

MaName = maoper51, PrimaryVlanid = 10
Test Description To verify that user is able to configure more than one Maintenance Associations
in a specified Maintenance Domain with different MA names with different
Primary VIDs.
Test Topology 2.8
Test Procedure
Create Maintenance Domain
2 Create Maintenance Association for MD = OP1 at level 1 Verify that there are two
MaName = maop1, PrimaryVlanId = 2 Maintenance association maop1
and maop2 exists at MD = OP1 at
Create Maintenance Association for MD = OP1 at level 1
level 1.
MaName = maop2, PrimaryVlanId = 3
3 Create Maintenance Association for MD = OP1 at level 1 Verify that MA maop1 is not created
MaName = maop1, PrimaryVlanId = 6 because there is already exists an
MA having the same name.
4 Create Maintenance Association for MD = OP1 at level 1 Verify that MA maop11 is not
MaName = maop11, PrimaryVlanId = 2 created because there is already
<AM3100>
CLI command: 2.10-13 exists an MA with the same primary

vid as MA maoper11.
5 Create Maintenance Association for MD = OP2 at level 2 Verify that MA maop1 is created in
MaName = maop1, PrimaryVlanId = 22 MD OP2 at level 2.
Test Description To verify that deletion of the Maintenance Association from the specified
Maintenance Domain is allowed only if there is no MEP configured in that
Maintenance Association.
Test Topology 2.8
Test Procedure
command: 2.10-18
Configure MaMepListTable of MA maop3 for MepId = 2 Cli command: 2.10-19
3 Create MEP at IGU port 2 of bridge DUT1 Verify that MEP at IGU port 2 can
MepId = 2, level = 3, VlanId = 9(maop3), Direction be created.
= Down CLI command: 2.10-20
4 Delete Maintenance Association with association id Verify that MA maop3 is not deleted.
maop3 Cli command: 2.10-19
5 Delete MEP from IGU port 2 of bridge DUT1 Verify that MEP is deleted.
6 Delete Maintenance Association with association id Verify that MA maop3 is deleted.
maop3 CLI command: 2.10-19
28 ARICENT:
REVISION HISTORY
Test Description To check that dot1agCfmMaMepList Table can only be configured for MEPIDs
between 1 and 8191.
Test Topology 2.8
Test Procedure
Create Maintenance Domain The maintenance domain should be
command: 2.10-18
Create Maintenance Association for MD = OP3 at level 3 Verify that MA maop3 is created in
with MD OP3 at level 3.
MaName = maop3, PrimaryVlanId = 2 Cli command: 2.10-19
Configure MaMepList Table of MA maoper6 for MepId = 1 Verify that MaMepList table is
CLI command: 2.10-20 configured for MepId = 1
Configure MaMepList Table of MA maoper6 for MepId = 0 Verify that MaMepList table is not
CLI command: 2.10-20 configured for MepId = 0
Configure MaMepList Table of MA maoper6 for MepId = Verify that MaMepList table is
8191 configured for MepId = 8191
Configure MaMepList Table of MA maoper6 for MepId = Verify that MaMepList table is not
8192 configured for MepId = 8192
Test Description 1. To test that MEP is created only when Ma/Md for which it is to be created
exists.
2. To test that Down MEP can be created.
Test Topology 2.8
Test Procedure
<AM3100>
1 Create MEP at IGU port 2. Verify that MEP cannot be created

MepId = 2, level = 6, VlanId = 20(maoper6), at IGU port 2.
Direction = Down CLI command: 2.10-20
MdName = oper6, MdLevel = 6 successfully created. This should
command: 2.10-18
3 Create Maintenance Association for MD = oper6 at level Verify that MA maoper6 is created in
6 with MD oper6 at level 3.
MaName = maoper6, PrimaryVlanId = 20 Cli command: 2.10-19
Configure dot1agCfmMaMepListTable of MA maoper6
for MepId = 2
4 Create MEP at IGU port 2. Verify that MEP at IGU port 2 can
MepId = 2, level = 6, VlanId = 20(maoper6), be created.
Direction = Down CLI command: 2.10-20
Test Description To check that MEP can be created only when MaMepList has an entry for this
Mep
To check that MEPID between 1 and 8191 are only allowed.
Test Topology 2.8
Test Procedure
command: 2.10-18
2 Create Maintenance Association for MD = OP6 at level 6 Verify that MA maoper6 is created in
with MD oper6 at level 3.
3 Configure MaMepList Table of MA maop6 for MepId = 0 Verify MaMepList Table do not have
CLI command: 2.10-13 the entry for MEPID =0.
4 Configure MaMepList Table of MA maop6 for MepId = Verify MaMepList Table do have the
8191 entry for MEPID =8191.
30 ARICENT:
REVISION HISTORY

5 Create down MEP at interface P2 with Verify that MEP exists with id 8191
MepId = 8191, level = 6, VlanId = 2 (maop6) at level 6 having association-id
maop6 at IGU port 2.
Test Description 1. To check that Vlan unaware down MEPs are allowed to create in the system.
2. To check that the creation of a Vlan unaware down MEP at the level greater
than the MD Level of the Vlan aware MP is not allowed.
3. To check that more than one Vlan unaware Down MEPs on an interface at
different MD level can be configured.
Test Topology 2.8
Test Procedure
Domain name = OP2, Domain level = 2 successfully created. This should
Domain name = OP4, Domain level = 4
with MD op2 at level 2
MaName = maop2, Vlan = 0 Verify that MA maop4 is created in
Configure MaMepList Table of MA maop2 for MepId = MD op4 at level 4
2 Verify that MA maop5 is created in
Create Maintenance Association for MD = OP4 at level MD op5 at level 5.
4 with Verify that MA maop7 is created in
MaName = maop4, Vlan = 0 MD op7 at level 7
Configure MaMepList Table of MA maop4 for MepId = 1 Verify that MA maop6 is created in
MD op6 at level 0.
Create Maintenance Association for MD = OP5 at level
5 with
Configure MaMepList Table of MA maop5 for MepId =
<AM3100>
10 Cli command: 2.10-19

7 with
MaName = maop7, PrimaryVlanId = 101,
MaMHFCreation = defMHFexplicit
6 with
MaName = maop6, Vlan = 0
Configure MaMepList Table of MA maoper6 for MepId =
11
3 Create MEP at IGU port 2 of bridge DUT1 Verify that Vlan aware MEP is
MepId = 10, Level = 5, VlanId = 4, Direction = created at level 5.
Down CLI command: 2.10-14
4 Create MIP at IGU port 2 Verify that MIP is created at level 7.
MdLevel = 7, Vid = 101 CLI command: 2.10-14
5 Create MEP at IGU port 2 of bridge DUT1 Verify that Vlan unaware MEP
MepId = 11, Level = 6, VlanId = 0, Direction = cannot be created because there is
Down a MIP configured at a higher level
and Vlan aware MEP configured at
the lower level on this interface.
6 Create MEP at IGU port 2 of bridge DUT1 Verify that Vlan unaware down MEP
MepId = 1, Level = 4, VlanId = 0, Direction = is created.
Down CLI command: 2.10-14
Create MEP at IGU port 2 of bridge DUT1 Verify that Vlan unaware down MEP
MepId = 1, Level = 2, VlanId = 0, Direction = is created.
7 CLI command: 2.10-14
Down
Test Description To check that MepIds are unique within a maintenance association
Test Topology 2.8
Test Procedure
Domain name = OP7, Domain level = 7 successfully created. This should
32 ARICENT:
REVISION HISTORY
Cli command: 2.10-12 command: 2.10-18

with MD op7 at level 7
MaName = maop2, PrimaryVlanId = 101 Verify that MA maop3 is created in
Configure MaMepList Table for MepId = 1,2 MD op7 at level 7
Create Maintenance Association for MD = OP7 at level Cli command: 2.10-19
7 with
Configure MaMepList Table for MepId = 1
3 1. Create Down MEP at IGU port 2 with Creation of Down MEP at IGU port
MepId = 1, level = 6, Vlan = 101 (maop2) 2 with MepId=1 should pass.
2. Create Down MEP at IGU port 2 with
MepId = 1, level = 6, Vlan = 11 (maop3)
CLI
command: 2.10-14
4 1. Create Down MEP at IGU port 2 with Creation of Down MEP at interface
MepId = 1, level = 6, Vlan = 101 (maop2) P1 with MepId=1 should fail since
the MepId =1 was already used for
2. Create Down MEP at IGU port 2 with maop1.
MepId = 1, level = 6, Vlan = 101 (maop2) CLI command: 2.10-14
Test Description To verify that MEP cannot be created if the MepId for this MEP is not in the MA’s
list of MepIds (MIB: dot1agCfmMaMepListTable).
Test Topology 2.8
Test Procedure
command: 2.10-18
2 Create Maintenance Association for MD = oper1 at level Verify that MA maop1 is created in
1 with MD oper1 at level 1
3 Create MEP at IGU port 2 with Creation of Down MEP at IGU port
<AM3100>
MepId = 1, level = 1, VlanId = 2 (maop1), Direction 2 with MepId=1 should fail.

= Down CLI command: 2.10-14
command: 2.10-14
Test Description To verify that MEP cannot be created if there exists a MEP in the opposite
direction at the same MD level, for the same VID(s).
Test Topology 2.8
Test Procedure
command: 2.10-18
Configure MaMepList Table of MA maoper6 for MepId
= 4,5
3 Create MEP at IGU port 2 of bridge DUT1 with Down MEP at Level = 3 and VlanId
MepId = 4, level = 3, VlanId = 3 (maop3), Direction = 3 is created at IGU port 2 of
= Down bridge DUT1.
command: 2.10-14 CLI command: 2.10-14
4 Create MEP at IGU port 2 of bridge DUT1 with Down MEP at Level = 3 and VlanId
MepId = 5, level = 3, VlanId = 3 (maop3), Direction = 3 is not created at IGU port 2 of
= Down bridge DUT1 since there is already
exists a Down MEP at Level = 3
and VlanId = 3.
Test Description To verify that primary vid of the MEP is always one of the VIDs assigned to the
MEPs MA.
Test Topology 2.8
34 ARICENT:
REVISION HISTORY
Test Procedure
command: 2.10-18
2 Configure dot1agCfmVlanTable The vlan-id’s 1, 2 & 3 should be
Set PrimaryVid = 9. for Vid = 1,2,3 successfully associated to primary-
vlan-id 9.
Configure MaMepList Table of MA maoper5 for MepId
= 1,2
4 Create MEP at IGU port 2 of bridge DUT1 with Verify that MEP is not created at
MepId = 1, level = 5, VlanId = 101 (maop5), MepId = 1, level = 5, VlanId = 101
Direction = Down since VlanId is not same as that of
MA maop5.
5 Create MEP at IGU port 2 of bridge DUT1 with Verify that MEP is created at MepId
MepId = 2, level = 5, VlanId = 9 (maop5), = 2, level = 5, VlanId = 9 since
Direction = Down VlanId is same as that of MA
maop6.
Test Description To verify that user is able to configure MIP for a MD on each port, all MIPs being
at the same MD Level for all MAs associated to this MD.
Test Topology 2.8
Test Procedure
command: 2.10-18
MaName = maop1, PrimaryVlanId = 2, Cli command: 2.10-19
Dot1agCfmMaMhfCreation = defMHFdefault
MaMeplist table = MepId 1.
<AM3100>

3 Create an Down MEP with MepId = 1 PrimaryVlanId = 2 Verify that MEP is created at MepId
at IGU port 2 = 1, level = 4, VlanId = 2.
4 Create MIP1 at IGU port 2 of bridge DUT1 with MIP is created at IGU port 2 of
Level = 4, VlanId = 2 bridge DUT1 at level = 4 and VlanId
=2
5 Create MIP 2 at IGU port 2 of bridge DUT1 with MIP is not created at IGU port 2 of
Level = 4, VlanId = 2 bridge DUT1 at level = 4 and VlanId
=2
Test Description To verify that MIP cannot be configured if there exists MEP at equal or higher
MdLevel on that port – case 1.
Test Topology 2.8
Test Procedure
MdName = oper3, MdLevel = 3
MaName = maop4, PrimaryVlanId = 2, Verify that MA maop3 is created in
dot1agCfmMaMHFCreation = defMHFdefault MD oper3 at level 3.
Configure MaMepList table for MepId = 1
Create Maintenance Association for MD = oper3 at
level 3 with
MaName = maop3,PrimaryVlanId = 7,
dot1agCfmMaMHFCreation = defMHFdefault
3 Create down MEP at IGU port 2 of bridge DUT1 with Verify that MEP is created at MepId
MepId = 1, level = 4, VlanId = 2 (maop4) = 1, level = 4, VlanId = 2.
4 Create MIP at IGU port2 of bridge DUT1 with MIP is not created at IGU port 2 of
MdLevel = 3, VlanId = 7 bridge DUT1 at Level = 3, VlanId =
7 due to the existence of MEP at
36 ARICENT:
REVISION HISTORY
CLI command: 2.10-14 the Level higher than that at which

MIP is to be configured
Test Topology 2.8
Test Procedure
2 Create Maintenance Association for MD = oper2 at level 2 Verify that MA maop2 is created in
with MD oper2 at level 2.
Verify that MA maop5 is created in
MD oper5 at level 5.
level 5 with Cli command: 2.10-19
3 Create MEP at IGU port2 of bridge DUT1 with MEP is created at interface P1 of
MepId = 1, level = 2, VlanId = 2 (maop5) bridge DUT1 at Level = 2 ,VlanId =
2
4 Create MIP at IGU port2 of bridge DUT1 with MIP is created at interface P1 of
MdLevel = 5, VlanId = 7 bridge DUT1 at Level = 5, VlanId =
7.
Test Topology 2.8
<AM3100>

Test Procedure
level 5 with
3 Create MIP at interface P1 of bridge DUT1 with MIP is created at interface P1 of

MdLevel = 5, VlanId = 7 (maop5) bridge DUT1 at Level = 5, VlanId =
7.
4 Create MEP at interface P1 of bridge DUT1 with MEP is created at interface P1 of
MepId = 1, level = 2, VlanId = 2 (maop2) bridge DUT1 at Level = 2 ,VlanId =
2
Test Topology 2.8
Test Procedure
38 ARICENT:
REVISION HISTORY
MdName = oper5, MdLevel = 5 command: 2.10-18

Create Maintenance Association for MD = oper5 at Cli command: 2.10-19
level 5 with
MaMHFCreation = defMHFdefault
3 Create MIP at interface P1 of bridge DUT1 with MIP is created at interface P1 of

MdLevel = 5, VlanId = 7 (maop5) bridge DUT1 at Level = 5, VlanId =
7.
4 Create MEP at interface P1 of bridge DUT1 with MEP is not created at interface P1
MepId = 1, level = 6, VlanId = 2 (maop6) of bridge DUT1 at Level = 6, VlanId
= 2 since it is at the higher level
than the MIP already created at
interface P1.
Test Topology 2.8
Test Procedure
command: 2.10-18
MaMHFCreation = defMHFdefault Cli command: 2.10-19
. Configure MaMepList Table of MA maop5 for MepId =
1
<AM3100>
3 Create MEP at IGU port 2 of bridge DUT1 with MEP is created at IGU port 2 of
MepId = 1, level = 5, VlanId = 1 (maop5) bridge DUT1 at level = 5, VlanId = 1
4 . Create MIP at IGU port 2 of bridge DUT1 with MIP is not created at IGU port 2 of
MdLevel = 5, VlanId = 1 bridge DUT1 at level = 5 since there
is MEP at the same level
Test Description To verify that user should not be able to create MIPs for a MA which is not
associated with any VID.
Test Topology 2.8
Test Procedure
command: 2.10-18
3 Create MIP at interface P1 of bridge DUT1 with MIP is not created at IGU port 2.
level = 1, VlanId = 0 (maop1)
Test Description To verify that Vlan unaware down MEP should be configured below LA.
To verify that Vlan aware Down MEP cannot be configured on the LA port
Test Topology 2.9
40 ARICENT:
REVISION HISTORY
Test Procedure
command: 2.10-18
Configure MaMepList Table for MepId = 1, 2 Cli command: 2.10-19
3 Link-Aggregate IGU port 2 & 3 to form linkagg1. Link-Aggregation group linkagg1

Cli command: 2.10-7 should be created successfully.
Cli command: 2.10-7
4 Create Down MEP at linkagg1 with Verify that vlan unaware down MEP
MepId = 1, level = 1, VlanId = 0 (maop1) at MepId = 1, level = 1 is not
created at linkagg1.
5 Create Down MEP at IGU port 2 with Verify that vlan unaware down MEP
MepId = 2, level = 1, VlanId = 0 (maop1) at MepId = 2, level = 1 is created at
interface P2.
command: 2.10-18
2 with MaName = maop2, Vlan = 2 MD oper2 at level 1.
Configure MaMepList Table for MepId = 1, 2
Cli command: 2.10-7
9 Create Down MEP at linkagg1 with Verify that vlan aware down MEP at
MepId = 1, level = 2, VlanId = 2 (maop2) MepId = 1, level = 2, vlan =2 is
created at linkagg1.
10 Create Down MEP at IGU port 2 with Verify that vlan aware down MEP at
MepId = 2, level = 2, VlanId = 2 (maop2) MepId = 2, level = 2, vlan =2 is not
created at IGU port 2.
Test Description To verify that MHF cannot be configured below LA.

<AM3100>
Test Topology 2.9

Test Procedure
command: 2.10-18
dot1agCfmMaMHFCreation = defMHFdefault Cli command: 2.10-19

Cli command: 2.10-7
4 Create MIP at port linkagg1 with Verify that MIP at level = 1, VlanId =
MdLevel = 1, VlanId = 3 3 is created at port linkagg1.
5 Create MIP at IGU port 2 with Verify that no MIP at level = 1 is
MdLevel = 1, VlanId = 3 created
Test To verify that MIPs are created dynamically.

Description
Test Topology 2.8
Test Procedure
1 1) Create Vlan 2 and configure IGU port 1 as Vlan 2 & 3 should be successfully
member port of Vlan 2. configured. This can be retrieved by
2) Create Vlan 3 and configure IGU port 2 as using the below cli command: 2.10-9
member port of Vlan
3) Cli command: 2.10-9
2 Set the MIP dynamic evaluation status to be true. The value should be successfully set to
42 ARICENT:
REVISION HISTORY
CLI command: 2.10-21 true.

3 Check whether the MIP is created or not for both the  Verify that dynamic MIP is not
vlans 2 & 3. created at MD Level = 0 with
CLI command: 2.10-20 Vlan =2 at port P1 as Default MD
Table variable
dot1agCfmDefaultMdMhfCreatio
n has the value defMHFdefer
and Scalar variable
dot1agCfmDefaultMdDefMhfCre
ation has the value as
defMHFnone.
 Verify that dynamic MIP is not
created at MD Level = 0 with
Vlan =3 at port P2 as Default MD
Table variable
dot1agCfmDefaultMdMhfCreatio
n has the value defMHFdefer
and Scalar variable
dot1agCfmDefaultMdDefMhfCre
ation has the value as
defMHFnone.
4 1) Set Scalar fsEcfmDefaultMdDefLevel is set as 5 Verify that MIP is created at MD Level =
for both the Vlans configured. 5 with Vlan =2 at port P1.
2) Set Scalar dot1agCfmDefaultMdDefMhfCreation Verify that MIP is created at MD Level =
is set as defMHFdefault for both the Vlans 5 with Vlan =3 at port P2.
configured. CLI command: 2.10-20

DomainName = OP3, Domain Level = 3 successfully created. This should be
command: 2.10-18
6 Create Maintenance Association for MD = OP3 at Verify that MA maop3 is created in MD
level 3 with OP3 at level 3.
Assoc-name = maop3, Vlanid = 2,
MaMhfCreation = none Cli command: 2.10-19
Create an entry of MEPID = 3 in MaMepListTable for
MA = maop3
7 Create down MEP at interface P1 A down MEP should be successfully
Mepid = 3, level = 3 Vlanid = 2 (maop2) created.
DomainName = OP4, Domain Level = 4 successfully created. This should be
command: 2.10-18
9 Create Maintenance Association for MD = OP4 at Verify that MA maop4 is created in MD
level 4 with OP4 at level 3.
MaMhfCreation = explicit Cli command: 2.10-19
<AM3100>

10 Set fsMIEcfmDefaultMdMhfCreation variable The value should be successfully set to
corresponding to PrimaryVid 2 in default Md Table defMHFExplicit.
as defMHFExplicit”.
11 Set fsMIEcfmDefaultMdLevel variable corresponding Verify that MIP is created at MD Level =
to PrimaryVid 2 in DefaultMd Table as 3 4 with Vlan = 2 at IGU port 2.
3.2 Continuity Check Messages – CCM

Test Description To check that CCM interval is allowed to be configured

Test Topology 2.8
Test Procedure
DomainName = OP1, DomainLevel = 1 successfully created. This should
command: 2.10-18
2 Create Vlan-id 2 and associate the IGU port 2 to it. Vlan 2 should be successfully
Cli command: 2.10-9 configured. This can be retrieved by
9
3
Assoc-name = maop1, Vlan = 2
Cli command: 2.10-13 Cli command: 2.10-19
4 Create down MEP at interface P1 The down MEP should be
successfully created and the default
mepid = 1, level = 1, vlanid = 2 (maop1)
ccm interval is set to 1 sec.
5 Configure CC with interval = 5 (10 sec) for Ma = maop1, Verify that CC Interval/transmission
MdLevel = 1 period is configured to 10 sec
CLI command: 2.10-21 Verify that CCM packets are being
transmitted every 10 sec
44 ARICENT:
REVISION HISTORY
Test Description To verify that CCM is successfully generated, transmitted, received.

Test Topology 2.8
Test Procedure
1 DUT1(AM3100): The maintenance domain should be
Create Maintenance Domain. successfully created. This should
DomainName = OP1, Domain Level = 1 command: 2.10-18
2 Create Vlan with Vlanid = 2 and configure IGU port 2 of Vlan 2 should be successfully
bridge as member port of this Vlan. configured. This can be retrieved by
Cli command: 2.10-9 using the below cli command: 2.10-
9
AssocName = maop1, Vlanid = 2 MD OP1 at level 1.
4 Create Down MEP at IGU port 2 of bridge with The down MEP should be
MepId = 1, Level = 1, VlanId = 2 (maoper1), successfully created.
MepActive = True Cli command: 2.10-20
5 ISS (Simulator): The maintenance domain should be
DomainName = OP1, Domain Level = 1
command: 2.10-18
6 Create Vlan with Vlanid = 2 and configure port 2 of Vlan 2 should be successfully
9
1 MD OP1 at level 1.
AssocName = maop1, Vlanid = 2
8 Create Down MEP at port 2 of bridge with The down MEP should be
9 Enable the CCM at IGU port 2 of AM3100. CCM PDU should be generated and
CLI command: 2.10-21 the CCM database should contain
the remote MEP id 2.
10 Enable the CCM at port 2 of ISS Simulator. CCM PDU should be generated and
<AM3100>
Test Description 1. To check that CCM are transmitted with common CFM header.
2. To check that CCM Packet size is in multiple of octets.
3.To verify that the CCM PDUs are transmitted with LLC header based on Ports
LLC- encapsulation status
Test Topology 2.8
Test Procedure
9
command: 2.10-18
9
46 ARICENT:
REVISION HISTORY
11 Verify the CCM packet received at ISS Simulator. 1) Verify that port P1 of the bridge is
transmitting CCM PDUs after every
1 second.
3) Observe the destination mac
address of the CCM PDUs is
“01:80:C2:XX:XX:X1”
4) Observe the source mac address
of the CCM PDUs are port mac
address P1
5) Observe the ether type of the
CFM packet is present
6) Observe the CFM header
consists of Mdlevel = 1, version = 0,
opcode = 1, Ccinterval as 1 in flags
7) Observe the Mepid=1 is present
in the CCM messages.
8) Observe the MAID consists of
MDNameformat = 4,
MDNamelength as 3, MDName as
OP1”
ShortMANameformat = 4,
ShortMANamelength = 5 and
ShortMAName as maop1” and
ensure the remaining of the MAID
are padded properly.
10) Observe that the SenderId TLV
with type =1 is present.
11) Observe that the Organizational
TLV with type = 31 is present.
12) Observe that the end TLV
consists of only zeros.
13) Observe the length of the CCM
packet is in multiple of octets.
12 Enable llc-encapsulation status for both the DUT’s. Verify that CCM PDU are
CLI command: 2.10-24 transmitted with LLC Header
<AM3100>
Test Description To verify that the CCM PDUs are transmitted with tag based on the port member
ship of the VLAN.
Test Topology 2.8
Test Procedure
9
command: 2.10-18
9
48 ARICENT:
REVISION HISTORY
11 Verify the CCM packet received at ISS Simulator. The CCM packet should contain the
vlan tag as 2 and Priority = 7.
12 Configure ccmltmpriority = 4 of MEPID = 10, level = 3, The CCM packet should contain the
Vlanid =2 vlan tag as 2 and Priority = 4.
13 Configure IGU port 2 as the untagged member port of the Verify that the CCM PDUs are
Vlanid = 2 transmitted without VLAN tag.
Test Description 1. To verify that for each CCM transmitted, CCISentCCMs are incremented
properly with sequence number present in the packet.
2. To verify that the change in CC Interval influences the periodicity of the
transmitted CCMs.
Test Topology 2.8
Test Procedure
9
<AM3100>

6 Verify the CCM packet received at ISS Simulator. Observe the transmitted CCM
packet on IGU port 2 consists of the
sequence number/ CCISentCCMs
is incrementing on every CCM
transmit.
7 Change the CCM interval to 1 min Observe the periodicity of CCMs, it
CLI command: 2.10-21 should be 1 min.
Test Description To verify the transmitted CCM contains proper MD name, MA name and MEP ID
configured for a MEP.
Test Topology 2.8
Test Procedure
9
MepId = 1, Level = 1, VlanId = 2 (maop1), successfully created.
6 Verify the CCM packet received at ISS Simulator. Observe the CCM packet received at
ISS Simulator.
MDNameformat = 4,
MDNamelength = 3, MDName =
OP1
50 ARICENT:
REVISION HISTORY
MANameformat = 4,
MANamelength = 20, MAName =
maop1
MEP ID = 1
Test Description To verify that the two MEPs in two different MA at two different interfaces can
transmit CCM messages at different interval.
Test Topology 2.8
Test Procedure
DomainName = OP1, Domain Level = 1 successfully created. This should
2 Create Vlan 2, 3 and configure IGU port 2 as member Vlan 2 & 3 should be successfully
port of Vlan 2 and 3 respectively. configured. This can be retrieved by
9
Assoc-name = maop1, Vlanid = 2, Verify that MA maop2 is created in
Create Maintenance Association for MD = OP2 at level 2 MD OP2 at level 2.
with
Create an entry of MEPID = 1, MEPID = 2 in
MaMepListTable.
Mepid = 1, level = 1, Vlanid = 2 (maop1) successfully created.
Create down MEP at interface P2 Cli command: 2.10-20
Mepid = 2, level =2, Vlanid = 3 (maop2)
5 Configure CC transmission interval to 10 seconds at IGU Verify that the CCM packet coming
port 2 for vlan 2. from MEP id 1 should be received at
Configure CC transmission interval to 1 second at IGU a periodicity of 1 sec.
port 2 for vlan 3. Verify that the CCM packet coming
Enable CCM for both the vlan’s. from MEP id 2 should be received at
CLI command: 2.10-21 a periodicity of 10 sec.
<AM3100>
Test Description To verify that the two MEPs in same MA at two different interfaces should
transmit CCM messages at same interval.
Test Topology 2.9
Test Procedure
command: 2.10-18
2 Create Vlan 2. Configure IGU port 2 & 3 as member port Vlan 2 should be successfully
of Vlan 2 respectively. configured. This can be retrieved by
9
MaMepListTable. Cli command: 2.10-19
Create down MEP at interface P2 Cli command: 2.10-20
5 Configure CC transmission interval to 10 seconds for Verify that the CCMs are transmitted
vlan 2 and enable CCM. from IGU port 1 and IGU port 2 of
CLI command: 2.10-21 AM3100 at an interval of 10
seconds.
6 Configure CC transmission interval to 1 second for vlan 2 Verify that the CCMs are transmitted
and enable CCM. from IGU port 1 and IGU port 2 of
AM3100 at an interval of 1 second.
Test Description . To verify that the operational status of the port reflects the values of Interface
Status TLV (up/down) 2. To also verify that the change in interface status cause
Mac status changed to true which results in transmission of extra CCM?
Test Topology 2.8
52 ARICENT:
REVISION HISTORY

Test Procedure
9
6 Verify the contents of the Interface – TLV Observe the CCM PDU transmitted
by each MEP with interface TLV as
up.
And verify that only one CCM PDU
should be transmitted in 1 sec by
each MEP configured on interface
P1.
7 Change the interface status (i.e. IGU port 2) to down. ISS Architectural constraint:
CCM will not be transmitted when
interface is down whether MEP is
Up/Down.
Test Description 1. To verify that the operational status of the port reflects the values of Port
Status TLV (up/blocked)
2. To also verify that the change in Port status cause Mac status changed to true
which results in transmission of extra CCM.
3. To verify that extra CCM will not be transmitted if the CC interval greater than
10 seconds
Test Topology 2.9
<AM3100>

4) RSTP should be enabled for both the DUT’s.
5) Configure the bridge-priority to be 4096 for DUT 2.
Test Procedure
1 AM3100(DUT1): The maintenance domain should be
Create Maintenance Domain successfully created. This should
2 Create Vlan 2 & 3. Configure IGU port 2 & 3 as member Vlan 2 & 3 should be successfully
port of Vlan 2 & 3 respectively. configured. This can be retrieved by
9
Assoc-name = maop1, Vlanid = 2,3,
4 Create down MEP at IGU port 2 The down MEP should be
Create down MEP at IGU port 2 Cli command: 2.10-20
5 Configure CC transmission interval to 1 second at IGU Verify that both MEPs are
port 2 and enable CCM. transmitting CCMs with port status
CLI command: 2.10-21 TLV as up on the interval of 1
second.
6 Configure the port priority of IGU port 3 as 32” Verify that both MEPs are
transmitting CCMs with port status
TLV as discarding on the interval of 1
second.
7 Configure the port priority of Port P2 as 128 and set the Verify that the CCM are transmitted
CCM interval to be 1 min. with port status TLV as forwarding.
No extra CCM should be transmitted
for the change in port status TLV.
Verify that the CCM are transmitted
at an interval of 1 min.
Test Description 1. To verify that the port Status TLV is sent when
a. When MST is disabled
b. When MST is enabled and MEP is vlan aware
2. Port status TLV can have two values Up or Blocked in transmitted CCM."
54 ARICENT:
REVISION HISTORY
Test Topology 2.9

4) MSTP should be enabled on DUT2.
5) RSTP should be enabled on DUT1.
Test Procedure
2 Create Vlan 2 & 3. Configure IGU port 2 & 3 as member Vlan 2 & 3 should be successfully
port of Vlan 2 & 3 respectively. configured. This can be retrieved by
9
Assoc-name = maop1, Vlanid = 2,3
5 Configure CC transmission interval to 1 second at IGU Verify that both MEPs are
port 2 and enable CCM. transmitting CCMs with port status
CLI command: 2.10-21 TLV as up on the interval of 1
second.
6 Configure the port priority of IGU port 3 as 32 Verify that both MEPs are
transmitting CCMs with port status
TLV on the interval of 1 second.
7 Enable MSTP on DUT1 and wait for 30 sec for the Verify that both MEPs are
topology to settle. transmitting CCMs with port status
TLV
8 Change bridge priority of DUT2 so that it becomes root Verify that both the MEP’s are
transmitting CCMs with appropriate
port status TLV. The value should be
discarding.
Test Description To verify that MEPactive should influence the transmission CCM messages by
MEP.
Test Topology 2.8
<AM3100>

Test Procedure
9
6 Configure the MEP Id =1, Level =1 status as “inactive”. Verify that no CCM PDU is
generated by the MEP in inactive
status.
Test Description 1. To verify that CCM messages will not be transmitted by the MEP, if the
VLAN is not present in the system.
2. To verify that CCM messages are transmitted untagged by the MEP, even
though the port is not a member of the VLAN configured for the MEP.
Test Topology 2.8
Test Procedure
56 ARICENT:
REVISION HISTORY

Cli command: 2.10-12 be retrieved by using the below cli
command: 2.10-18
Assoc-name = maop1, Vlanid = 2, MD OP1 at level 7.
Create an entry of MEPID = 1 in MaMepListTable.
3 Create down MEP at IGU port 2 with The down MEP should be
4 Configure CC enabled status for MEP at IGU port 2 with Verify that the CCMs are not
Mepid = 1, level =7, Vlanid = 2 as enabled transmitted by the MEP at IGU port
CLI command: 2.10-21 2 with Mepid =1, level =7, Vlanid =2
5 Create Vlan 2 with member port as IGU port 2. Verify that the CCMs are
Cli command: 2.10-9 transmitted by the MEP at IGU port
2 with Vlan tag (Vlanid =2, priority
=7)
6 Configure Vlan 2 with member port as IGU port 3. Verify that the CCMs are
Cli command: 2.10-9 transmitted by the MEP at IGU port
2 with no Vlan tag
Test Description To verify that whether the CCM PDU contains the Sender Id TLV or not.
Test Topology 2.8
Test Procedure
9
<AM3100>
MepActive = True
6 Set dot1agCfmMaIdPermission Verify that CCM PDU should
(MIB:dot1agCfmMaTable) to sendIdChassis contain sender Id TLV (Chassis Id
TLV)
7 Set dot1agCfmMaIdPermission Verify that CCM PDU should not
(MIB:dot1agCfmMaTable) to sendIdDefer contain sender Id TLV
Set dot1agCfmMdMhfIdPermission
(MIB:dot1agCfmMdTable) to sendIdNone
(MIB:dot1agCfmMaTable) to sendIdDefer contain sender Id TLV (Manage
Set dot1agCfmMdMhfIdPermission address TLV)
(MIB:dot1agCfmMdTable) to sendIdManage
(MIB:dot1agCfmMaTable) to sendIdDefer contain sender Id TLV (Chassis Id,
Set dot1agCfmMdMhfIdPermission Manage address TLV)
(MIB:dot1agCfmMdTable) to sendIdChassisManage
Test Description To verify that RDI bit is set in the transmitted CCM PDU by MEP, if defect
entered in Dot1agCfmMepDefects entry of the dot1agMepTable has higher
priority than dot1agCfmMepLowPrDef in dot1agCfmMepTable.
Test Topology 2.8
Test Procedure
DomainName = Customer1, Domain Level = 7 successfully created. This should
command: 2.10-18
2 Create Vlan with Vlanid = 2 and configure IGU port 2 as Vlan 2 should be successfully
member port of this Vlan. configured. This can be retrieved by
9
3 Create Maintenance Association for MD = Customer1 at Verify that MA maop1 is created in
level 7 with MD Customer1 at level 1.
Assoc-name = maop1, Vlanid = 2 , CC Interval = 4.
Create an entry of MEPID = 1000, MEPID = 7 in Cli command: 2.10-19
58 ARICENT:
REVISION HISTORY
MaMepList Table.
mepid = 1000, level = 7, Vlanid = 2 (maop1) , MepActive successfully created.
= True Cli command: 2.10-20
5 Enable CC at IGU port 2 with in next CCM Interval Expiry CCM PDU should be generated
(3.5 sec) to have the defect for the MacStatus otherwise Cli command: 2.10-20
we will have the defects for RemoteCCM fault.
6 From Ixia port 1 to IGU port 2, Transmit CCM with Verify that CCM PDU generated by
destination_address as the group address MEP = 1000 at IGU port 2 will have
01:80:C2:XX:XX:X7” for Mdlevel = 7, Vlanid =2, priority = the RDI bit = 1 as CCM sent from
7, MEPID = 7 ,Interface status TLV is 2 Ixia port 1 will set the 2nd bit in
Dot1agCfmMepDefects entry of the
dot1agMepTable because of
MacStatusCCM defect.
“01:80:C2:XX:XX:X7” for Mdlevel = 7, Vlanid =2, priority the RDI bit = 1 as CCM sent from
= 7, MEPID = 1000 ,Interface status TLV is 1 Ixia port 1 will set the 4th bit in
ErrorCCM defect.
01:80:C2:XX:XX:X4” for Mdlevel = 4, Vlanid =2, priority = the RDI bit = 1 as CCM sent from
7, MEPID = 7, Interface status TLV is 1 Ixia port 1 will set the 5th bit in
XconCCM defect
01:80:C2:XX:XX:X7” for Mdlevel = 7, Vlanid =2, priority the RDI bit = 1 as CCM sent from
=7, MEPID = 7, Interface status TLV is 1 ixia port 1 will set the 3rd bit in
RemoteCCM defect
Test Description To verify that:

a. Vlan unaware MEP generate CCM without Port Status TLV when MST is
enabled
b. Port status TLV should be transmitted when MST is disabled (RST enabled)
Test Topology 2.9
<AM3100>

4) Enable MSTP for the bridge.
Test Procedure
command: 2.10-18
Assoc-name = maop1, Vlanid = 0
Create an entry of MEPID = 1 in MaMepListTable Cli command: 2.10-19
Mepid = 1, level = 1, Vlanid = 0 (maop1), MepActive = successfully created.
True Cli command: 2.10-20
4 Enable CCM at IGU port 2 for MEP =1 at level =1, Vlanid Verify that CCMs PDU do not
= 0. contain port status TLV when
CLI command: 2.10-21 generated by unaware Vlan MEP at
IGU port 2 on Bridge (DUT1).
5 Enable RSTP on Bridge. Verify that CCMs PDU contain port
Wait for 30 sec for topology to settle. status TLV when generated by
unaware Vlan MEP at IGU port 2 on
Bridge (DUT1).
Test Description To check that CCMs transmitted are no longer than 128 octets in length
Test Topology 2.8
Test Procedure
command: 2.10-18
60 ARICENT:
REVISION HISTORY
Set dot1agCfmMaIdPermission in MaTable as the value

sendIdChassisManage
4 Enable CCM at IGU port 2 for MEP =1 at level =1, Vlanid 1) Verify the destination mac
= 2. address of the CCM PDU’s is
CLI command: 2.10-21 01:80:C2:FF:FF:F1”
2) Observe the source mac address
of the CCM PDUs are port mac
address P1
3) Observe the CFM header
consists of Mdlevel = 1, version = 0,
opcode = 1, Ccinterval as 1 in flags”
4) Observe the mepid=1 is present
in the CCM messages.
MDNameformat = 4,
MDNamelength as 3, MDName as
OP1”
ShortMANameformat = 4,
ShortMANamelength = 5 and
ShortMAName as maop1” and
ensure the remaining of the MAID
are padded properly.
7) Observe that the Port Status TLV
with type =2 is present
8) Observe that the Interface Status
TLV with type =4 is present
9) Observe that the SenderId TLV
with type =1 is present.
10) Observe that the Organizational
TLV with type = 31 is present.
11) Observe that the end TLV
consists of only zeros.
12) Verify that length of CCM PDU
is less then 128 octets.
Test Description 1. To verify that CCM is processed if received CCM PDU's MD Level is less than
or equal to receiving MEPs MD Level.
2. To verify that CCM is discarded if received CCM PDU's MD Level is greater
<AM3100>
then receiving MEP’s MD Level.

Test Topology 2.8
Test Procedure
1) Create Maintenance Domain successfully created. This should
DomainName = OPER5, Domain Level = 5 be retrieved by using the below cli
2) Create Maintenance Domain command: 2.10-18
DomainName = OPER6, Domain Level = 6
3) Create Maintenance Domain
DomainName = OPER7, Domain Level = 7
member port of Vlan 6 respectively. configured. This can be retrieved by
9
3 Create Maintenance Association for MD = OPER5 at level Verify that MA maop5 is created in
5 with MD OPER5 at level 5.
Assoc-name = maop5, Vlanid = 6, Verify that MA maop6 is created in
Create Maintenance Association for MD = OPER6 at level MD OPER6 at level 6.
6 with Verify that MA maop7 is created in
Assoc-name = maop6, Vlanid = 6, MD OPER7 at level 7.
Create Maintenance Association for MD = OPER7 at level
7 with
Assoc-name = maop7, Vlanid = 6, Cli command: 2.10-19
Create an entry of MEPID = 5, MEPID = 6, MEPID = 7 in
MaMepListTable.
Mepid = 5, level = 5, Vlanid = 6 , MepActive = True successfully created.
Mepid = 6, level = 6, Vlanid = 6 , MepActive = True
Create down MEP at IGU port 2 Mepid = 7, level = 7,
Vlanid = 6, MepActive = True
5 ISS Simulator: The maintenance domain should be
DomainName = OPER6, Domain Level = 6 be retrieved by using the below cli
6 Create Vlan with Vlanid= 6 and configure ports P1 as Vlan 6 should be successfully
9
7 Create Maintenance Association for MD = OPER6 at Verify that MA maop6 is created in
62 ARICENT:
REVISION HISTORY
level 6 with MD OPER6 at level 6.

Create an entry of MEPID = 10 in MaMepListTable
Mepid = 10, level = 6, Vlanid = 6 (maop6), successfully created.
9 Enable CC at IGU port 2 for MEPID = 5 Verify that CCM PDU is processed
CLI command: 2.10-21 and 5th bit in
dot1agMepTable is set for
DefXconCCM on interface P1 of
ISS Simulator.
10 Disable CC enable at IGU port 2 for MEPID = 5 Verify that CCM PDU is processed
Enable CC at interface IGU port 2 for MEPID = 6 and CCM Database (Entry in Table
Dot1agCfmMepDbEntry) is updated
for the received CCM on interface
P1 of ISS Simulator.
11 Disable CC enable at IGU port 2 for MEPID = 6 Verify that CCM PDU is discarded
Enable CC at interface IGU port 2 for MEPID = 7 on interface P1 of OP2 and verify
that CCM Database (Entry in Table
Dot1agCfmMepDbEntry) is not
updated for the received CCM PDU.
Test Description To verify that valid CCM PDU received having MD Level equal to receiving
MEP's MD Level will be stored in MEP CCM Database
a. MAC address of the remote MEP (the source_address of the last received
CCM) otherwise 0 should be present if no CCM has been received.
b. State of the RDI bit (true for RDI = 1), otherwise false if none has been
received.
c. Port Status TLV if present, otherwise the default value psNoPortStateTLV
should be present.
d. Interface Status TLV if present, otherwise the default value
isNoInterfaceStatusTLV should be present.
e. Chassis ID Subtype , Chassis ID, Management Address Domain and
Management Address in the received CCM if present , otherwise the default
value isNoSenderIdTLV should be present.
Test Topology 2.8
Test Procedure
<AM3100>

1) Create Maintenance Domain successfully created. This should be
DomainName = OPER6, Domain Level = 6 retrieved by using the below cli
member port of Vlan 6 respectively. configured. This can be retrieved by
using the below cli command: 2.10-9
3 Create Maintenance Association for MD = OPER6 at level Verify that MA maop6 is created in
6 with MD OPER6 at level 6.
MaMepListTable.
Mepid = 5, level = 6, Vlanid = 6 , MepActive = True successfully created.
Create Maintenance Domain successfully created. This should be
DomainName = OPER6, Domain Level = 6 retrieved by using the below cli
6 Create Vlan with Vlanid= 6 and configure ports P1 as Vlan 6 should be successfully
using the below cli command: 2.10-9
7 Create Maintenance Association for MD = OPER6 at Verify that MA maop6 is created in
level 6 with MD OPER6 at level 6.
Mepid = 6, level = 6, Vlanid = 6 (maop6), MepActive successfully created.
= True Cli command: 2.10-20
9 Enable CC at IGU port 2 for MEPID = 5 Verify that the MEP database of ISS
CLI command: 2.10-21 Simulator is updated with the below
contents:
Verify that dot1agMepDbTable has
the entries for
dot1agCfmMepDbMacAddress =
Host A mac address
dot1agCfmMepDbRdi = True
dot1agCfmMepDbPortStatusTlv = 2
dot1agCfmMepDbInterfaceStatusTlv
=1
64 ARICENT:
REVISION HISTORY
Test Description To verify that FID (Filtering Identifier), source address and Port number of
received CCM is stored in MIP CCM Database if received CCM PDUs MD Level
is equal to receiving MHFs MD Level.
To verify that CCM is forwarded if received CCM PDU's MD Level is less or
greater then receiving MHFs MD Level.
Test Topology 2.8
Test Procedure
DomainName = OP4, Domain Level = 4 be retrieved by using the below cli
2 Create Vlan with Vlanid = 4 and configure port P1 as Vlan 4 should be successfully
member ports of this Vlan configured. This can be retrieved by
cli command: 2.10-9 using the below cli command: 2.10-
9
Assoc-name = maop4, Vlanid = 4, MD OP4 at level 4.
Dot1agCfmMaMhfCreation = defMHFdefault Cli command: 2.10-19
4 Create MIP at IGU port 2 with A MIP can be successfully created
Port index = 3, level = 4, vlanid = 4 (maop4) at IGU port 2.
6 Create Vlan with Vlanid = 4 and configure port P1 as Vlan 4 should be successfully
member ports of the Vlan 4 respectively configured. This can be retrieved by
9
Assoc-name = maop3, Vlanid = 4 MD OP3 at level 3.
MD OP4 at level 4.
Verify that MA maop5 is created in
Create Maintenance Association for MD = OP5 at level 5 MD OP5 at level 5.
Create an entry of MEPID= 3, MEPID= 4, MEPID= 5 in
<AM3100>
MaMepListTable Cli command: 2.10-19

8 Create down MEP at interface P1 with The down MEPs should be
MEPID = 3 , level = 3, Vlanid = 4 (maop3), MepActive = successfully created.
Create down MEP at interface P1 with
MEPID = 4 , level = 4, Vlanid = 4 (maop4), MepActive =
True
Create down MEP at interface P1 with
MEPID = 5 , level = 5, Vlanid = 4 (maop5), MepActive =
True
9 Enable CC for MEPID = 3 at interface P1 of ISS Verify that CCM is received by
Simulator. down MHF at IGU port 2 is
CLI command: 2.10-21 forwarded and MIP CCM Database
is not updated.
10 Disable CC enable for MEPID = 3 at interface P1 of ISS Verify that CCM is received by
Simulator. down MHF at IGU port 2 and MIP
Enable CC for MEPID = 4 at interface P1 of ISS CCM Database is updated.
Simulator.
11 Disable CC enable for MEPID = 4 at interface P1 of ISS Verify that CCM is received by
Simulator. down MHF at IGU port 2 is
Enable CC for MEPID = 5 at interface P1 of ISS forwarded and MIP CCM Database
Simulator. is not updated.
Test Description To verify CCMsequenceErrors should be incremented by 1 for every out-of-

sequence CCM PDU received.
Test Topology 2.8
Test Procedure
DomainName = customer1, Domain Level = 3 successfully created. This should be
command: 2.10-18
2 Create Vlan with Vlanid = 2 and configure port IGU port Vlan 2 should be successfully
2 as member port of this Vlan. configured. This can be retrieved by
9
66 ARICENT:
REVISION HISTORY
3 Create Maintenance Association for MD = customer1 at Verify that MA maop1 is created in

level 3 with MD customer1 at level 3.
Assoc-name = maop1, Vlanid = 2, CCM Interval = 6 (1 Cli command: 2.10-19
min),
Create an entry of MepId = 1, MepId = 4 in
MaMepListTable
4 Create down MEP at IGU port 2 The down MEPs should be
5 From Ixia port 1 (or) ISS Simulator. Verify that MEP CCM Database has
Transmit CCM with destination_address as the group Sequence Number as 1, Note the
address 01:80:C2:XX:XX:X3” for Mdlevel = 3, Vlanid =2, value of
priority = 7, MepId = 4 , Sequence no = 1. dot1agCfmMepCcmSequenceErrors
is equal to zero.
6 Transmit CCM with destination_address as the group Verify that MEP CCM Database has
address 01:80:C2:XX:XX:X3” for Mdlevel = 3, Vlanid =2, Sequence Number as 2, Note the
priority = 7, MepId = 4, Sequence no = 2 value of
dot1agCfmMepCcmSequenceErrors
is equal to zero.
7 Transmit CCM with destination_address as the group Verify that MEP CCM Database has
address 01:80:C2:XX:XX:X3” for Mdlevel = 3, Vlanid =2, Sequence Number as 3, Note the
priority = 7, MepId = 4, Sequence no = 3 value of
dot1agCfmMepCcmSequenceErrors
is equal to zero.
8 With in the next CCM Interval expiry (1 min Transmit Verify that CCM PDU is processed
another CCM PDU with destination_address as the and
group address 01:80:C2:XX:XX:X3” for Mdlevel = 3, dot1agCfmMepCcmSequenceErrors
Vlanid =2, priority = 7, MepId = 4, Sequence no = 5. has been updated on IGU port 2.
Test Description Verify that CCM PDU of more than 128 octets in length should be discarded
Test Topology 2.8
Test Procedure
DomainName = customer1, Domain Level = 3 successfully created. This should be
command: 2.10-18
2 Create Vlan with Vlanid = 2 and configure port IGU port Vlan 2 should be successfully
2 as member port of this Vlan. configured. This can be retrieved by
<AM3100>
cli command: 2.10-9 9

min),
MaMepListTable
5 From Ixia port 1 (or) ISS Simulator. Verify that MEP CCM Database has
Transmit CCM with destination_address as the group Sequence Number as 1, Note the
address 01:80:C2:XX:XX:X3” for Mdlevel = 3, Vlanid =2, value of
priority = 7, MepId = 4 , Sequence no = 1. dot1agCfmMepCcmSequenceErrors
is equal to zero.
6 Transmit CCM with destination_address as the group Verify that CCM PDU is discarded
address 01:80:C2:XX:XX:X3” for Mdlevel = 3, Vlanid =2, on interface IGU port 2.
priority = 7, MepId = 4, Sequence no = 2 and CCM PDU
length to be greater than 128 octets.
Test Description To verify fault DefErrorCMM is generated.

a) Mep id doesn’t match the MaMeplist table.
b) Mep id is same as the Mep id in the received CCM
c) CCM interval field doesn’t match.
Test Topology 2.8
Test Procedure
DomainName = customer1, Domain Level = 3 command: 2.10-18
2 Create Vlan with Vlanid = 2 and configure port IGU port 2 Vlan 2 should be successfully
as member port of this Vlan. configured. This can be retrieved by
9
min),
68 ARICENT:
REVISION HISTORY

MaMepListTable
DomainName = customer1, Domain Level = 3 command: 2.10-18
6 Create Vlan with Vlanid = 2 and configure port 1 as Vlan 2 should be successfully
9
min),
Create an entry of, MepId = 2, 3 in MaMepListTable
8 Create down MEP at port 1 The down MEPs should be
9 Enable CCM for MEP 2(ISS Simulator) & MEP(DUT1). As MEP-id 2 is not present in the
CLI command: 2.10-21 MaMepList table of DUT1, fault
DefErrorCMM is generated.
10 Delete the MEPid = 2 in the ISS Simulator. The Down MEP can be successfully
deleted.
12 Enable CCM for the MEP 1 in ISS Simulator. As the MEP id is same the MEP id
received the CCM, fault
DefErrorCMM is generated.
13 Delete the Mep id = 1 in the ISS Simulator. The Down MEP can be successfully
deleted.
15 Set the CCM interval to 15 sec. As the CCM interval doesn’t match,
CLI command: 2.10-21 fault DefErrorCMM is generated.
<AM3100>
Test Description To verify fault DefXconCCM is generated

a) MA id doesn’t match.
b) MD level of received CCM is less than the received MEP’s MD level.
Test Topology 2.8
Test Procedure
DomainName = name1, Domain Level = 6 be retrieved by using the below cli
9
3 Create Maintenance Association for MD = name1 at level Verify that MA maop1 is created in
6 with MD name1 at level 6.
dot1agMaCcmInterval = 5
MaMepListTable
4 Create down MEP at interface IGU port 2 The down MEPs should be
Mep Id = 1, level = 6, Vlanid = 5 (maop1), MepActive = successfully created.
True. Cli command: 2.10-20
5 ISS Simulator (CASE 1): The maintenance domain should be
6 Create Vlan with Vlanid = 5 and configure ports P1 as Vlan 5 should be successfully
9
Create Maintenance Association for MD = name1 at level Verify that MA maop2 is created in
7
MaMepListTable
8 Create down MEP at interface P1 The down MEPs should be
70 ARICENT:
REVISION HISTORY

9 Enable CCM for the interface P1 of ISS Simulator. Verify that CCM PDU is received
CLI command: 2.10-21 from MEPID=1, Fault DefXconCCM
is generated and 5th bit is set in
entry Dot1agCfmMepDefects of the
dot1agMepTable on interface IGU
port 2.
10 ISS Simulator (CASE 2): The maintenance domain should be
11 Create Vlan with Vlanid = 5 and configure ports P1 as Vlan 5 should be successfully
9
MaMepListTable
13 Create down MEP at interface P1 The down MEPs should be
14 Enable CCM for the interface P1 of ISS Simulator. Verify that CCM PDU is received
CLI command: 2.10-21 from MEPID=1, Fault DefXconCCM
port 2.
Test Description To verify DefRDICCM fault is generated if:

a. RDI bit of the received CCMs are true.
Test Topology 2.9
Test Procedure
<AM3100>

9
MaMepListTable
4 Create down MEP at interface IGU port 2 The down MEPs should be
9
Create Maintenance Association for MD = name1 at level Verify that MA maop1 is created in
7
9 Enable CCM for the IGU port 2 in DUT1. Verify that CCM PDU is received
CLI command: 2.10-21 from MEPID=1, Fault DefErrorCCM
port 1 of DUT2.
10 Enable CCM for the IGU port 1 in DUT 2. Verify that CCM PDU is received
CLI command: 2.10-21 from MEPID=1, Fault DefRDICCM
is generated and 1st bit is set in
port 2 of DUT1.
72 ARICENT:
REVISION HISTORY
Test Description To verify DefMACstatus fault is generated if

a. Interface status in any of the received CCMs from any remote MEP is not
"isUP", or
b. Port Status TLV in all of the received CCMs from all the remote MEPs is other
than "psUp".
Test Topology 2.8
3) Bridge-mode should be set to Provider-edge.
Test Procedure
command: 2.10-18
9
with MD maop1 at level 3.
MaMepListTable
5 From ixia port 1 to IGU port 2 of DUT1, Transmit CCM Verify that CCM PDU is processed
with destination_address as the group address and 2nd bit for DefMacStatus is not
01:80:C2:XX:XX:X3 for Mdlevel = 3, Vlanid =2, priority = set in entry Dot1agCfmMepDefects
7, MepId = 10, Sequence No = 1. of the dot1agMepTable on interface
IGU port 2 of DUT1.
6 From ixia port 1 to IGU port 2 of DUT1, Transmit CCM Fault DefMacStatus is generated
with destination_address as the group address and 2nd bit is set in entry
01:80:C2:XX:XX:X3 for Mdlevel = 3, Vlanid =2, priority = Dot1agCfmMepDefects of the
7, MepId = 10, Sequence No = 2 , Interface status TLV is dot1agMepTable on interface IGU
2. port 2 of DUT1.
7 From ixia port 1 to IGU port 2 of DUT1, Transmit CCM Verify that CCM PDU is processed
with destination_address as the group address and 2nd bit for DefMacStatus is not
01:80:C2:XX:XX:X3 for Mdlevel = 3, Vlanid =2, priority = set in entry Dot1agCfmMepDefects
7, MepId = 10, Sequence No =3. of the dot1agMepTable on interface
IGU port 2 of DUT1.
8 From ixia port 1 to IGU port 2 of DUT1, Transmit CCM Fault DefMacStatus is generated
with destination_address as the group address and 2nd bit is set in entry
01:80:C2:XX:XX:X3 for Mdlevel = 3, Vlanid =2, priority = Dot1agCfmMepDefects of the
<AM3100>
7, MepId = 10, Sequence No = 4, Port status TLV is 1. dot1agMepTable on interface IGU

port 2 of DUT1.
Test Description 1) To verify DefRemoteCCM fault is generated if a. 3 consecutive valid CCMs

are not received from a particular remote MEP
2) To verify MIB Trap (dot1agCfmFaultAlarm) is triggered if defect is present for
more than fngAlarmTime
Test Topology 2.9
Test Procedure
9
with Assoc-name = maop1, Vlanid = 2, CC Interval = 4 (1 MD OP2 at level 3.
sec) Cli command: 2.10-19
MaMepListTable
Mepid = 4, level = 3, vlanid = 2 (maop1) , MepActive = successfully created.
9
Assoc-name = maop1, Vlanid = 2, CC Interval = 4 (1 Cli command: 2.10-19
74 ARICENT:
REVISION HISTORY
sec)
MaMepListTable
8 Create down MEP at IGU port 1. The down MEPs should be
9 Enable CC for MEPID = 4 at IGU port 2 of DUT1. Verify that CCM PDU is not
CLI command: 2.10-21 received from MEPID=8, Fault
DefRemoteCCM is generated and
3rd bit is set in entry
Dot1agCfmMepDefects of the
dot1agMepTable on IGU port 2 of
DUT1.
Wait for fngAlarmTime (2.5
seconds)
MIB Trap (dot1agCfmFaultAlarm) is
triggered if defect DefRemoteCCM
is present for more than
fngAlarmTime.
Test Description To verify that LBM and LBR is successfully generated and transmitted - MEP
Test Topology 2.9
Test Procedure
9
MaMepListTable
<AM3100>
successfully created.
Mepid = 4, level = 3, vlanid = 2 (maop1) , MepActive = Cli command: 2.10-20
True
9
MaMepListTable
9 Initiate a loopback message from IGU port 1 of DUT2 to A loopback reply is received by the
DUT1. IGU port 1 from DUT1.
Test Description To verify that LBM and LBR is successfully generated and transmitted - MIP
Test Topology 2.9
Test Procedure
9
76 ARICENT:
REVISION HISTORY

9
Assoc-name = maop1, Vlanid = 2 Cli command: 2.10-19
Dot1agCfmMaMhfCreation = defMHFdefault
8 Create MIP at IGU port 1 with The MIP should be successfully
Port index = 3, level = 3, vlanid = 2 (maop1) created.
Test Description To verify that Vlan-unaware down MEP should be able to initiate the LBM
transmission.
Test Topology 2.8
Test Pre-requisite 1) AM3100 should be up and running.
Test Procedure
1 AM3100(DUT1): The maintenance domain
Create Maintenance Domain should be successfully
DomainName = OP2, Domain Level = 3 created. This should be
Cli command: 2.10-12 retrieved by using the below cli
command: 2.10-18
2 Create Maintenance Association for MD = OP2 at level 3 with Verify that MA maop1 is created
Assoc-name = maop1, Vlanid = 0. in MD OP2 at level 3.
<AM3100>

Mepid = 4, level = 3, vlanid = 0 (maop1) , MepActive = True successfully created.
4 Initiate the LBM Transmission at IGU port 2 of DUT1 by setting: Untagged LBM is generated at
a. No. of LBM PDUs to send IGU port 2 of DUT1.
[MIB:
dot1agCfmMepTable::dot1agCfmMepTransmitLbmMessages].
Set it to ‘1’.
b. Destination Address as the Mac Address of the port 1.
c. MD Level as 3
d. VlanId as 0
e. Value for Data TLV -–testing”
Test Description 1. To verify that LBM PDU generated by MEP should contain the following
fields :
Destination Address as the Individual Mac Address
Source Address as the Individual Mac Address of the transmitting MEP
MD Level as that of the transmitting MEP
Loopback Transaction ID as the value of the nextLBMTransID
Opcode as LBM
Data TLV
Sender Id TLV
Organization-Specific TLV
2. To verify that the LBM PDUs are transmitted with LLC header based on
Ports LLC- encapsulation status
3. To verify that for each LBM transmitted by a MEP, nextLBMTransID are
correctly incremented by 1 and copied into the Loopback Transaction ID
field present in the LBM PDU.
Test Topology 2.8
Test Procedure
Cli command: 2.10-12 retrieved by using the below cli
command: 2.10-18
78 ARICENT:
REVISION HISTORY
member port of this Vlan. configured. This can be

cli command: 2.10-9 retrieved by using the below cli
command: 2.10-9
3 Create Maintenance Association for MD = OP2 at level 3 with Verify that MA maop1 is created
Assoc-name = maop1, Vlanid = 2. in MD OP2 at level 3.
5 Initiate the LBM Transmission at IGU port 2 of DUT1 by setting: Tagged LBM is generated at
a. No. of LBM PDUs to send IGU port 2 of DUT1.
[MIB:
dot1agCfmMepTable::dot1agCfmMepTransmitLbmMessages].
Set it to ‘1’.
b. Destination Address as the Mac Address of the port 1.
c. MD Level as 3
d. VlanId as 2
e. Value for Data TLV -–testing”
6 Configure Port LLC-encapsulation status for IGU port 2 as 1. LBM PDU is generated at
“enabled. Interface IGU port 2 and it
CLI command: 2.10-24 should contains the following
fields:
a. Destination Address as the
Mac Address of the Interface
port 1.
b. Source Address as the Mac
Address of the Interface IGU
port 2.
c. MD Level as 3
d. VlanId as 2
e. Loopback Transaction Id as
the value of nextLBMtransID
f. Opcode as LBM
g. Data TLV
h. Sender Id TLV
i. Organization-Specific TLV
j. End TLV consists of zero
only
k. Verify that LBM PDU are
transmitted with LLC Header
Test Description To verify that LBM PDU contain the Data TLV if it is provided by the user.
Test Topology 2.9
<AM3100>

Test Procedure
9
MaMepListTable
9
MaMepListTable
Value for Data TLV - testing” CLI command: 2.10-25
(Through SNMP, set dot1agCfmMepLbmTransmitDataTlv
to “testing”)
80 ARICENT:
REVISION HISTORY
Value for Data TLV – no value CLI command: 2.10-25

(Through SNMP, set dot1agCfmMepLbmTransmitDataTlv
to “testing”)
Test Description To verify that LBM is transmitted only when port is ready to transmit
another LBM after transmitting previous LBMs.
Test Topology 2.9
Test Procedure
Cli command: 2.10-12 retrieved by using the below
cli command: 2.10-9 retrieved by using the below
cli command: 2.10-9
3 Create Maintenance Association for MD = OP2 at level 3 with Verify that MA maop1 is
Assoc-name = maop1, Vlanid = 2, CC Interval = 4 (1 sec) created in MD OP2 at level 3.
Create an entry of MEPID = 4, MEPID = 8 in MaMepListTable Cli command: 2.10-19
Cli command: 2.10-12 retrieved by using the below
cli command: 2.10-9 retrieved by using the below
cli command: 2.10-9
7 Create Maintenance Association for MD = OP2 at level 3 with Verify that MA maop1 is
Assoc-name = maop1, Vlanid = 2, created in MD OP2 at level 3.
<AM3100>

9 Initiate a loopback message from IGU port 1 of DUT2 to DUT1. A loopback reply is received
a. No. of LBM PDUs to send by the IGU port 1 from DUT1.
[dot1agCfmMepTable::dot1agCfmMepTransmitLbmMessages].
Set it to ‘20’.
b. Destination Address as the MAC Address of the IGU port 1
of DUT2.
c. MD Level as 3
d. VlanId as 2
e. Value for Data TLV-Testing”
10 Initiate a loopback message from IGU port 1 of DUT2 to DUT1. The command rejected and no
Value for Data TLV – no value LBM will be sent (because the
(Through SNMP, set dot1agCfmMepLbmTransmitDataTlv to Bridge is busy with another
“testing”) LBM transmit operation).
Test Description 1. To verify that LBR is generated by MEP if

a. MD level in the received LBM is identical to the MD level of the Receiving MEP.
b. Destination Address is either the Mac address of the receiving MEP or CCM
Group Address appropriate to the receiving MEPs MD Level.
c. Source Address is the individual Mac address
2. To verify that for every transmitted LBR the counter LbrOut [MIB:
dot1agCfmMepTable::dot1agCfmMepLbrOut] is getting incremented correctly by 1.
Test Topology 2.9
Test Procedure
DomainName = OP2, Domain Level = 3 retrieved by using the below cli command:
Cli command: 2.10-12 2.10-18
2 Create Vlan with Vlanid = 2 and configure IGU port 2 as Vlan 2 should be successfully configured.
member port of this Vlan. This can be retrieved by using the below cli
cli command: 2.10-9 command: 2.10-9
3 Create Maintenance Association for MD = OP2 at level 3 with Verify that MA maop1 is created in MD OP2
Assoc-name = maop1, Vlanid = 2, CC Interval = 4 (1 sec) at level 3.
4 Create down MEP at IGU port 2 The down MEPs should be successfully
82 ARICENT:
REVISION HISTORY
Mepid = 4, level = 3, vlanid = 2 (maop1) , MepActive = created.

Cli command: 2.10-12 2.10-18
Assoc-name = maop1, Vlanid = 2, at level 3.
8 Create down MEP at IGU port 1. The down MEPs should be successfully
9 Initiate a loopback message from IGU port 1 of DUT2 to DUT1. A loopback reply is received by the IGU port
a. No. of LBM PDUs to send 1 from DUT1.
Set it to ‘20’.
of DUT2.
c. MD Level as 3
d. VlanId as 2
10 Initiate a loopback message from IGU port 1 of DUT2 to DUT1. 1. A loopback reply is received by the IGU
a. No. of LBM PDUs to send port 1 from DUT1.
[dot1agCfmMepTable::dot1agCfmMepTransmitLbmMessages]. 2. Compare the current value of counter

Set it to ‘20’. LbrOut [MIB:
b. Destination Address as the CCM group address particular dot1agCfmMepTable::dot1agCfmMepLbrOut]
to the MD level. for MEP at interface IGU port 1 of DUT2.
c. MD Level as 3
d. VlanId as 2
Test Description To Check The LBR generated by MEP for the received LBM contains
a. Source Address as the MEP's MAC Address
b. Destination Address same as the Source Address in the received LBM
c. MD Level as in the received LBM
d. VlanId as in the received LBM
<AM3100>
e. Opcode as LBR
f. Flag bit same as in the received LBM
g. Loopback Transaction Id as in the received LBM
h. Data TLV as in the received LBM
i. Sender Id TLV as in the received LBM
j. Organization-Specific TLV as in the received LBM
k. Priority bit same as in received LBM.
Test Topology 2.9
Test Procedure
Cli command: 2.10-12 2.10-18
Cli command: 2.10-12 2.10-18
a. Destination Address as the MAC Address of
84 ARICENT:
REVISION HISTORY
[dot1agCfmMepTable::dot1agCfmMepTransmitLbmMessages]. the Interface IGU port 2 of DUT1.

Set it to 1’. b. Source Address as the MAC Address of the
b. Destination Address as the MAC Address of the IGU port 1 Interface IGU port 1 of DUT2.
of DUT2. c. MD Level (as in LBM)
c. MD Level as 3 d. VlanId (as in LBM)
d. VlanId as 2 e. Opcode as LBR
e. Value for Data TLV-Testing” f. Loopback Transaction Id (as in LBM)
CLI command: 2.10-25 g. Data TLV (as in LBM)
h. Sender Id TLV (as in LBM)
i. Organization-Specific TLV (as in LBM)
j. End TLV consists of zero only
Test Description 1. To verify that LBR is generated by MIP if

a. MD level in the received LBM is identical to the MD level of the Receiving MIP.
b. Destination Address is either the Mac address of the receiving MIP or CCM
Group Address appropriate to the receiving MIPs MD Level.
c. Source Address is the individual Mac address
2. To verify that for every transmitted LBR the counter LbrOut [MIB:
dot1agCfmMepTable::dot1agCfmMepLbrOut] is getting incremented correctly by 1.
Test Topology 2.9
Test Procedure
Cli command: 2.10-12 2.10-18
<AM3100>
Cli command: 2.10-12 2.10-18
Assoc-name = maop1, Vlanid = 2 at level 3.
8 Create MIP at IGU port 1 with The MIP should be successfully created.
Port index = 3, level = 3, vlanid = 2 (maop1)
Set it to ‘20’.
of DUT2.
c. MD Level as 3
d. VlanId as 2
10 Initiate a loopback message from IGU port 1 of DUT2 to DUT1. 1. A loopback reply is received by the IGU
a. No. of LBM PDUs to send port 1 from DUT1.
[dot1agCfmMepTable::dot1agCfmMepTransmitLbmMessages]. 2. Compare the current value of counter

Set it to ‘20’. LbrOut [MIB:
b. Destination Address as the CCM group address particular dot1agCfmMepTable::dot1agCfmMepLbrOut]
to the MD level. for MEP at interface IGU port 1 of DUT2.
c. MD Level as 3
d. VlanId as 2
Test Description To Check The LBR generated by MIP for the received LBM contains
a. Source Address as the MIP's MAC Address
b. Destination Address same as the Source Address in the received LBM
c. MD Level as in the received LBM
d. VlanId as in the received LBM
86 ARICENT:
REVISION HISTORY
e. Opcode as LBR
f. Flag bit same as in the received LBM
g. Loopback Transaction Id as in the received LBM
h. Data TLV as in the received LBM
i. Sender Id TLV as in the received LBM
j. Organization-Specific TLV as in the received LBM
k. Priority bit same as in received LBM.
Test Topology 2.9
Test Procedure
Cli command: 2.10-12 2.10-18
Cli command: 2.10-12 2.10-18
a. Destination Address as the MAC Address of
[dot1agCfmMepTable::dot1agCfmMepTransmitLbmMessages]. the Interface IGU port 2 of DUT1.
Set it to 1’. b. Source Address as the MAC Address of the
<AM3100>
of DUT2. Interface IGU port 1 of DUT2.

c. MD Level as 3 c. MD Level (as in LBM)
d. VlanId as 2 d. VlanId (as in LBM)
e. Value for Data TLV-Testing” e. Opcode as LBR
CLI command: 2.10-25 f. Loopback Transaction Id (as in LBM)
g. Data TLV (as in LBM)
h. Sender Id TLV (as in LBM)
i. Organization-Specific TLV (as in LBM)
j. End TLV consists of zero only
Test Description a. To verify that the in-sequence counter is correctly incremented by 1 if the Loopback
Transaction ID in the received LBR is equal to the expected LBR's transaction id.
b. To verify that the out-of-sequence counter is correctly incremented by 1 if the
Loopback Transaction ID in the received LBR is not equal to the expected LBR's
transaction id.
Test Topology 2.9
Test Procedure
Cli command: 2.10-12 2.10-18
Cli command: 2.10-12 2.10-18
88 ARICENT:
REVISION HISTORY

Verify that dot1agCfmMepLbrIn (for MEP at
[dot1agCfmMepTable::dot1agCfmMepTransmitLbmMessages]. interface IGU port 2) is incremented by 1.
Set it to 1’. CLI command: 2.10-25
of DUT2.
c. MD Level as 3
d. VlanId as 2
10 Again initiate a loopback message from IGU port 1 of DUT2 to Verify that LBR with Loopback Transaction
DUT1. ID = 3 is received as expected. If not, then
LBM(Loopback Transaction Id = 2) is generated at interface IGU value of dot1agCfmMepLbrInOutOfOrder is
port 1 with Loopback Transaction ID = 2. incremented by 1.
Send a LBR with Loopback Transaction Id = 3 from IGU port 2 of
DUT1.
Test Description To verify that a dot1agCfmMepLbrBadMsdu counter is incremented if the contents of

the received LBR (except Opcode) is not matched with the contents of the LBM of the
matching Loopback Transaction Identifier.
Test Topology 2.9
Test Procedure
Cli command: 2.10-12 2.10-18
<AM3100>

Cli command: 2.10-12 2.10-18
9 Initiate a loopback message from IGU port 1 of DUT2 to DUT1. A loopback message is successfully
a. No. of LBM PDUs to send generated.
Set it to 1’.
of DUT2.
c. MD Level as 3
d. VlanId as 2
10 Generate a LBR from IGU port 2 of DUT1 with Data TLV – abc. Observe the current values of
dot1agCfmMepLbrBadMsdu. It should be
incremented by 1.
Test Description 1. To Verify Transmitted LTM contains :

a. Destination address as Multicast address (01-80-C2-xx-xx-xy) where "y"
mentioning the MD Level of the transmitting MEP.
b. Source address as the MAC address of the transmitting MEP
c. Priority parameter same as that of CCMs
d. Opcode Field should contain value as 5 "LTM"
e. If the LTM needs to use the FDB of the bridge to be forwarded UseFDBOnly bit
90 ARICENT:
REVISION HISTORY
should be set. Reserved values should be Zero

f. First TLV Offset value is 17
g. LTM Transaction Identifier Field.
h. LTM TTL field greater than ZERO.
i. Original mac Address is individual mac Address of MEP
j. Target mac Address is individual mac Address of MP.
k. LTM Egress Identifier of the Linktrace Initiator
l. End LTV as "0"
2. To verify A new entry in the LTM Reply List is made for the transmitted LTM, indexed by the
LTM Transaction identifier.
3. To verify nextLTMtransID value is incremented after the LTM is transmitted.
Test Topology 2.9
Test Procedure
Cli command: 2.10-12 2.10-18
Cli command: 2.10-12 2.10-18
<AM3100>
9 Initiate a linktrace message from IGU port 2 of DUT1 to DUT1. A linktrace reply should be received for the
linktrace message.
10 Verify the linktrace message received at IGU port 1 of DUT2. a. Destination address is Multicast address
(01-80-C2-ff-ff-fd)
b. Source address is “MEP” mac address (of
IGU port 2 of DUT1).
c. Priority parameter is 4
d. Opcode Field should contain 5
e. UseFDBOnly bit is set. Reserved values
are Zero
f. First TLV Offset value is 17
g. LTM Transaction Identifier Field.
h. LTM TTL 64. (Default)
i. Original mac Address is “MEP” mac
address (IGU port 2 of DUT1)
j. Target mac Address is mac address of
(IGU port 1 of DUT2)
k. LTM Egress Identifier of the Linktrace
Initiator
l. End LTV as "0"
Test Description To verify that invalid LTM messages are rejected by the system.
Test Topology 2.9
Test Procedure
Cli command: 2.10-12 2.10-18
92 ARICENT:
REVISION HISTORY
Cli command: 2.10-12 2.10-18
9 Initiate a linktrace message from IGU port 2 of DUT1 to DUT1 with Verify that the linktrace message is rejected
time-to-live set to 256. by the system.
10 Initiate a linktrace message from IGU port 2 of DUT1 to DUT1 with Verify that the linktrace message is rejected
LTM flag set to 256. by the system.
Test Description To verify that LTMs received are valid LTM.

a) Destination address parameter of LTM should be group address appropriate to the MDlevel
field in the LTM. (OR)
b) Destination address parameter of LTM is the Individual MAC address of receiving MEP.
Test Topology 2.8
Test Procedure
Cli command: 2.10-12 2.10-18
<AM3100>

5 Generate LTM message for Mdlevel = 3 (Destination mac LTR should be not received since the
address = 01:80:C2:XX:XX:XB), Vlan =2 and Target mac transmitted LTMs Destination address is not
address is “MEP” mac address , LTM Transaction identifier as appropriate to the MDlevel of the receiving
10, LTM TTL should be set as 5”from ixia port 1. MEP
Test Description To Test that LTR will be transmitted exactly after 1 sec from the time of receiving the LTM.
To Test that Terminal MEP bit of the LTR should be set to 1 if the MP reported in Reply Ingress
is a MEP.
Test Topology 2.8
Test Procedure
Cli command: 2.10-12 2.10-18
5 Generate LTM message for Mdlevel = 3 (Destination mac LTR will be received with LTR flags
address = 01:80:C2:XX:XX:XB), Vlan =2 and Target mac UseFDBonly bit (MSB) as in LTM, FwdYes
address is “MEP” mac address , LTM Transaction identifier as bit (7th Bit) is unset, TerminalMep bit (6th
10, LTM TTL should be set as 5”from ixia port 1. Bit) is set and Rest bits (5-0) as in LTM.
Reply TTL, one less than the TTL received
in the LTM. Relay Action = 1 (RlyHit) in LTR
94 ARICENT:
REVISION HISTORY
and the Reply IngreeTLV is a contains MEP

Mac Address.
Test Description 1. To verify that the transmitted LTR contains

Opcode of LTR is 4
LTR flag with UseFDBonly bit (MSB) as in LTM, FwdYes bit (7th Bit) is
unset, TerminalMep bit (6th Bit) is set and Rest bits(5-0) as in LTM.
First TLV Offset is 6
All reserved fields as "0"
LTR Transaction Identifier same as LTM Transaction Identifier in received
LTM
Reply TTL, one less than the TTL received in the LTM
Relay Action = 1(RlyHit)
LTR Egress Identifier TLV with
Type = 8, Length = 16, Last Egress Identifier is same as Egress Identifier
field of the LTM Egress Identifier TLV of received LTM,
Next Egress Identifier that identifies the Responder
Organizational TLV (if receives in LTM then should be copied to LTR)
2. To verify that received LTM is discarded (not forwarded) if the LTM TTL field
contains the value 0.
Test Topology 2.8
Test Procedure
Cli command: 2.10-12 2.10-18
5 Generate LTM message for Mdlevel = 3 (Destination mac LTR should be received from the configured
address = 01:80:C2:XX:XX:XB), Vlan =2 and Target mac Down MEP.
address is “MEP” mac address , LTM Transaction identifier as
Opcode of LTR is 4
10, LTM TTL should be set as 5”from ixia port 1.
LTR flag should contain UseFDBonly bit
<AM3100>
(MSB) as in LTM FwdYes bit(7th Bit) is

unset, TerminalMep bit (6th Bit) is unset and
Rest bits(5-0) as in LTM.
First TLV Offset is 6
LTR should contain Terminal Bit to be set as
“1” and all other flags field should be set to
zero.
LTR should contain the transaction identifier
same as the LTM transaction identifier.
Relay Action = 1(RlyHit)
LTR should also contain the TTL value as
63 i.e one less than the TTL received in the
LTM
LTR Egress Identifier TLV with
Type = 8, Lendth = 16, Last Egress Identifier
is same as Egress Identifier
field of the LTM Egress Identifier TLV of
received LTM,
Next Egress Identifier that identifies the
Responder
and Organizational TLV present in
transmitted LTR.
6 Generate LTM message for Mdlevel = 3 (Destination mac LTM received is discarded without
address = 01:80:C2:XX:XX:XB), Vlan =2 and Target mac processing as the LTM TTL field contains
address is “MEP” mac address , LTM Transaction identifier as the value 0 So Verify no LTR is received.
10, LTM TTL = 0 should be set as 5”from ixia port 1.
Test Description To verify that LTR will respond to the LTM even though the CC enabled status of the MEP is
disabled.
Test Topology 2.9
Test Procedure
Cli command: 2.10-12 2.10-18
96 ARICENT:
REVISION HISTORY
Cli command: 2.10-12 2.10-18
9 Configure CC enabled status for MEP(Mepid = 4) at interface IGU CCM can be successfully enabled for IGU
port 2 as enable. port 2.
10 Configure CC enabled status for MEP(Mepid = 8) at interface IGU CCM can be successfully enabled for IGU
port 1 as enable. port 1.
11 Generate LTM message for Mdlevel = 3 (Destination mac A LTR should be successfully received from
address = 01:80:C2:XX:XX:XB), Vlan =2 and Target mac IGU port 1.
10, LTM TTL = 5 should be set as 5 from IGU port 2.
12 Disable the MEP active status for MEP id 4. The status of MEP should be successfully
set to Disabled.
Test Description To verify that LTMs are processed by the MEP if and only if MEP is in active state.
Test Topology 2.9
Test Procedure
<AM3100>

Cli command: 2.10-12 2.10-18
Cli command: 2.10-12 2.10-18
10 Disable the MEP active status for MEP id 8. The status of MEP should be successfully
set to Disabled.
11 Generate LTM message for Mdlevel = 3 (Destination mac A LTR should not be received from IGU port
address = 01:80:C2:XX:XX:XB), Vlan =2 and Target mac 1 as the MEP is in Inactive state.
Test Description 1. To verify that LTMs are discarded if the MD Level in PDU is Less Than MD Level of
receiving MEP
2. To verify that LTMs are replied with LTR if the MDlevel contained in the LTM is equal to the
98 ARICENT:
REVISION HISTORY
MDlevel of the receiving MEP

3. To verify LTMs are forwarded as a multicast data frame if the MD Level contained in PDU is
greater than MD Level of receiving MEP
Test Topology 2.8

Test Procedure
Cli command: 2.10-12 2.10-18
5 Generate LTM message for Mdlevel = 2 (Destination mac Verify that LTM should be discarded as the
address = 01:80:C2:XX:XX:XA), Vlan =2 and Target mac MD level is 2.
6 Generate LTM message for Mdlevel = 3 (Destination mac A LTR should be successfully received at
7 Generate LTM message for Mdlevel = 4 (Destination mac Verify that LTM should not be discarded and
address = 01:80:C2:XX:XX:XC), Vlan =2 and Target mac it should be forwarded as the MD level is
address is “MEP” mac address , LTM Transaction identifier as greater.
Test Description 1. To verify that LTMs are replied with LTR if the MDlevel contained in the LTM is equal
to the MDlevel of the receiving MHF
2. To verify that LTMs are not replied with LTR if the MDlevel contained in the LTM is not
equal to the MDlevel of the receiving MHF
Test Topology 2.9
<AM3100>

Test Procedure
Cli command: 2.10-12 2.10-18
Cli command: 2.10-12 2.10-18
10 Generate LTM message for Mdlevel = 4 (Destination mac The LTM packet should be discarded by the
address = 01:80:C2:XX:XX:XC), Vlan =2 and Target mac MIP as the MD level doesn’t match.
Test Description To verify that If the FDB does not have the unique egress port for the target mac address
Then LTMs are not responded with LTR.
100 ARICENT:
REVISION HISTORY
Test Topology 2.8

Test Procedure
Cli command: 2.10-12 2.10-18
5 Generate LTM message for Mdlevel = 3 (Destination mac Verify that no LTR is received.
address = 01:80:C2:XX:XX:XA), Vlan =2 and Target mac
address is some mac-address , LTM Transaction identifier as
Test Description 1. If the target Mac address of the received LTM is equal to the receiving Down MEP
Mac address,
(a) Verify LTR is generated on the received port irrespective of the spanning tree
port state of the LTM.
(b) Verify LTM is not Forwarded.
2. To verify that
(a) If the destination mac address of received LTM is multicast address appropriate to
MD level of the Down MEP and
(b) If the target mac address of received LTM is not the Mac address of the Down
MEP and
(c) If the spanning tree state of the Bridge Port and vlan_identifier of the LTM is not
Forwarding,
Then LTR is not generated on the received port.
Test Topology 2.9
<AM3100>

4) RSTP should be enabled for both the DUT.
Test Procedure
Cli command: 2.10-12 2.10-18
2 Create Vlan with Vlanid = 2 and configure IGU port 2 & 3 as Vlan 2 should be successfully configured.
member port of this Vlan. Observe that IGU port 2 should be This can be retrieved by using the below cli
in discarding state. command: 2.10-9
cli command: 2.10-9
Cli command: 2.10-12 2.10-18
address = 01:80:C2:XX:XX:XB), Vlan =2 and Target mac IGU port 1 irrespective of the discarding
address is “MEP” mac address , LTM Transaction identifier as state of IGU port 2 in DUT1.
10, LTM TTL should be set as 5”from IGU port 1.
10 Generate LTM message for Mdlevel = 3 (Destination mac Verify that the LTM packet should be
address = 01:80:C2:XX:XX:XB), Vlan =2 and Target mac discarded by the MEP in DUT1.
address is some mac address, LTM Transaction identifier as
102 ARICENT:
REVISION HISTORY
Test Description To verify that

(a) If the destination mac address of received LTM is multicast address appropriate to
MD level of the receiving Down MEP and
(b) If the target mac address of received LTM is not the mac address of the receiving
Down MEP and
(c) Using the FDB database If unique egress port is found
Then LTR is generated for the MEP Linktrace SAP
Test Topology 2.9
4) Connect a ISS simulator to DUT2(IGU port 2).
Test Procedure
Cli command: 2.10-12 2.10-18
cli command: 2.10-9
Cli command: 2.10-12 2.10-18

9 Generate LTM message for Mdlevel = 3 (Destination mac A LTR should be successfully received.
address = 01:80:C2:XX:XX:XB), Vlan =2 and Target mac
<AM3100>

10 Generate LTM message for Mdlevel = 3 (Destination mac A LTR should not be received as the Mac-
address = 01:80:C2:XX:XX:XB), Vlan =2 and Target mac address of ISS simulator is not learnt in the
address is Mac-address of ISS Simulator , LTM Transaction FDB table.
identifier as 10, LTM TTL should be set as 5”from IGU port 1.
11 Initiate ping from ISS Simulator with some ip-addr (say The mac-address should be learnt in the
20.1.1.1). DUT2.
12 Generate LTM message for Mdlevel = 3 (Destination mac LTR will be received with source Mac
address = 01:80:C2:XX:XX:XB), Vlan =2 and Target mac Address = “down MEP” mac address
address is Mac-address of ISS Simulator , LTM Transaction (DUT2), LTR flag’s UseFDBonly bit (MSB)
identifier as 10, LTM TTL should be set as 5”from IGU port 1. as in LTM, FwdYes bit (7th Bit) is set,
TerminalMep bit (6th Bit) is unset and Rest
bits (5-0) as in LTM. Reply TTL, one less
than the TTL received in the LTM. Relay
Action = 2 (RlyFDB) in LTR.
Test Description To verify that MIP replies with a LTR irrespective of the port-status.
Test Topology 2.9
4) RSTP should be enabled for both the DUT.
Test Procedure
Cli command: 2.10-12 2.10-18
member port of this Vlan. cli command: 2.10-9 This can be retrieved by using the below cli
command: 2.10-9
104 ARICENT:
REVISION HISTORY
Cli command: 2.10-12 2.10-18
cli command: 2.10-9

address = 01:80:C2:XX:XX:XB), Vlan =2 and Target mac IGU port 1 irrespective of the discarding
address is “MIP” mac address , LTM Transaction identifier as state of IGU port 2 in DUT1.
10 Generate LTM message for Mdlevel = 3 (Destination mac Verify that the LTM packet should be
address = 01:80:C2:XX:XX:XB), Vlan =2 and Target mac discarded by the MIP in DUT1.
address is some mac address, LTM Transaction identifier as
Test Description Verify that down MEP can be configured on linkagg.

Test Topology 2.9
Test Procedure
Cli command: 2.10-12 2.10-18
2 Create Vlan with Vlanid = 2. configure IGU port 2 & 3 as a Vlan 2 & linkagg should be successfully
linkagg and member port of this Vlan. configured. This can be retrieved by using
cli command: 2.10-9 the below cli command: 2.10-9
4 Create down MEP at linkagg port. The down MEPs should be successfully
<AM3100>

Cli command: 2.10-12 2.10-18
6 Create Vlan with Vlanid = 2. configure IGU port 1 & 2 as Vlan 2 and linkagg port should be
linkagg port and member port of this Vlan. successfully configured. This can be
cli command: 2.10-9 retrieved by using the below cli command:
2.10-9
8 Create down MEP at linkagg port. The down MEPs should be successfully
9 Generate LTM message for Mdlevel = 3 (Destination mac LTR should be successfully received.
address = 01:80:C2:XX:XX:XB), Vlan =2 and Target mac
10, LTM TTL should be set as 5”from linkagg port.
Revision History
Revisio Date Description of Author Reviewed & Approved By

n No. Change
1 11-Jan- Initial Creation of Prasanna
2010 the document Gopal.
106 ARICENT:

ECFM System Test Plan

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

ECFM System Test Plan

Uploaded by

Copyright:

Available Formats

<AM3100> aricent.

DOCUMENT No.: ARICENT:

ECFM SYSTEM TEST PLAN 1

Figure 0-1: TEST SETUP 1........................................................................................................................ 18

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

 The system is tested as a whole from the perspective of the users

 The testing would be conducted on a target platform similar to the

Table Introduction-1: Acronyms Used in this Document

1. NEC-A outsourcing proposal –SOW from Aricent.

ECFM SYSTEM TEST PLAN 8

2.1 Objective of Test

2.2 Test Method

ECFM SYSTEM TEST PLAN 11

Following test are the negative test cases

Other test cases

Ixia Traffic Generator/Analyzer.

<Specify the testing tool used to measure coverage >

ECFM SYSTEM TEST PLAN 12

2.3 Entry and Exit Criteria for System Testing

2.3.1 Entry Criteria

 Unit testing and integration testing complete

2.3.2 Exit Criteria

 System testing complete.

2.4 Test Schedule

As defined in the project plan.

2.5 Fault Reporting and Monitoring Progress

2.6 Build Plan and Build Refresh Criteria

A new build of the software is made whenever

ECFM SYSTEM TEST PLAN 13

2.7 Resource Requirements

2.7.1 Hardware Requirements

Table Test Plan-2: Hardware Requirements

Resource Quantity Descripti

2.7.2 Software Requirements

Table Test Plan-3: Software Requirements

Software Description Qty

ECFM SYSTEM TEST PLAN 15

AM 3100 IGU Port 0/3

IGU Port 0/1

ECFM SYSTEM TEST PLAN 17

AM 3100 IGU Port 0/5 AM 3100

IGU Port 0/2 & 3

IGU Port 0/4 FE/GE

FE/GE Port 1 Port 2 FE/GE

ECFM SYSTEM TEST PLAN 18

2.10 - Test Configurations

3 iss# write startup-config For save and Restore

ECFM SYSTEM TEST PLAN 19

Iss(config)# no ethernet cfm enable level.

21 To associate a set of vlans to the primary

iss(config)# no ethernet cfm cc enable level 1

iss# traceroute ethernet mac <interface mac

ECFM SYSTEM TEST PLAN 21

3.1 – Configuration Testcases

Test Description To check whether CFM should be enabled/disabled globally.

Test Case Id ECFM_SYS_FN_ 2

Test Description 1. To check creation of Maintenance Domain at a particular level.

ECFM SYSTEM TEST PLAN 23

Test Case Id ECFM_SYS_FN_ 3

ECFM SYSTEM TEST PLAN 24

CLI command: 2.10-12 created.

Test Case Id ECFM_SYS_FN_ 4

Test Case Id ECFM_SYS_FN_ 5