Feature Deployment and Testing Guide

IEEE802.1ag and ITU-T Y.1731

Feature ID: ZWF22-03-009

V3.11.10

ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2012 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 2012-8-3 First eition

Serial Number: SJ-20120802112720-133

Publishing Date: 2012-08-03(R1.0)

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

 Contents
Chapter 1 Functional Description ............................................................. 1-1
Chapter 2 Preparations .............................................................................. 2-1
Chapter 3 Data configuration .................................................................... 3-1
Chapter 4 Testing ....................................................................................... 4-1
4.1 Test Purpose...................................................................................................... 4-1
4.2 Steps for Test..................................................................................................... 4-1
4.3 Expected Results ............................................................................................... 4-5

Chapter 5 Counter List............................................................................... 5-1

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

 II

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

 Chapter 1
Functional Description
Bridges are increasingly used in Ethernet networks operated by multiple independent
organizations, each with restricted management access to each others equipment.
IEEE802.1ag connectivity fault management (CFM) function can provide capabilities for
detecting, verifying and isolating connectivity failures in such networks listed below:

1. Continuity Check: Multicast unidirectional heartbeat used for fault detection, mainly
for service level end to end continuity monitoring.
2. Loopback: Unicast bi-directional request/response for path continuity check between
local and peer maintenance end point. Used for fault detection and verification.
3. Link Trace: Similar with trace route function of IP protocol for route trace and record.
Used for fault isolation.
4. Performance management: monitoring the related KPI such as delay, packet loss rate
jitter etc. The implementation entity is MEP or MIP.
As an Ethernet technology, IEEE802.1ag is only applicable to Ethernet interface board.
The outer Ethernet port can only act as Maintenance End Point. Due to restriction
of software realization, IEEE802.1ag can only be deployed in VLAN tagged Ethernet
transmission scenarios temporarily.

Board supported by RNC: GIPI3 GIPI4.

IEEE802.1ag
IEEE 802.1ag,connectivity fault management can apply effective function for virtual bridge
LAN network fault check, isolation, verification and report. For the convenience of network
management and maintenance, the whole network topology should be planned according
to service and administrative levels into multi management domains shown as the following
figure:
Single Domain scenario

1-1

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF22-03-009

The management objects of domain mainly consists of MEP and MIP. The ports at the edge
of each domain can be defined as MEP(maintenance end points) which are connected
with the nodes outside this domain. The ports interior to domain are defined as MIP(
maintenance intermediate points) which are connected with internal equipments.
When layer 2 network planning is applied for RAN(Radio Access Network), RNC act as
customer equipment at the edge, so its outer Ethernet ports can only be configured as
MEP instead of MIP.

Ethernet work can be divided into multi-level domains includes customer domain,provider
domain. operator domain etc, Each domain must be configured with a dedicate level value
ranging from 0 to 7. The domains with higher level may comprise of several domains with
lower level. While lower level domains can not includes domains with higher or equal level
value. That is to say,the domains with the largest spectrum must be configured with the
highest level. The topology of adjacent domains can only be touching or nested instead
of intersection, as shown in the following figure:
Multiple Domains scenario

1-2

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

 Chapter 1 Functional Description

User can configure RNCs Ethernet port (SubSystem, Module, Unit, SUnit, LocalPort)) as
MEP, and the domain (MDINDEX, MDNAME) it homed should be user domain with highest
level (LEVEL).

Maintenance association(MA) is group of MEPs under the same MD (MD) served for
a dedicate service instance. MA is identified by parameter (MAID). MA is also basic
management entity for the network topology consists of a group MEPs. In each MD,
multiple MA can be created to maintenance multi CFM instances.
In the RAN network plan, a service instance is usually identified by a unique VLAN tag
(VLANID), and a MA is also used to corresponding to a dedicate VLAN. So for most
scenarios one MA is uniquely corresponding to a VLAN ID. On each MA object, user can
configure the continuity check management packets sending period (CCMPERIOD) for
the homed MEPs.

For a point to point service instance, the corresponding MA consists of two MEPs. For
a point to multi point service instance, the corresponding MA must consists of multiple
MEPs. Each virtual connection between two MEPs is called Maintenance entity, which is
the least CFM unit.
Local MEP remote MEP and their homed MD and MA info (MEPTYPE, MDINDEX,
MAINDEX, RMEPINDEX, MEPINDEX, MEPID) should be configured to guarantee
the continuity check between MEPs in the same MA. For remote MEP, MAC address
(MEPMAC)should also be configured. Continuity check can be implemented based on
each MEPs CCM message reception.
On OMCR, configuration switch (CCMSEND) and (CCMRCV) is provided to control
local MEP send CCM packets and receive CCM packets from peer MEP. The VLAN
tagged CCM packets 802.1P priority (PRIORITY)can also be assigned by user. Once
CCM send and receive function is enabled, local MEP will transmit CCM packets to peer

1-3

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF22-03-009

periodically(CCMPERIOD), and check continuity by monitoring CCM packets reception,

once connectivity fault is detected, corresponding alarm will be triggered.The supported
alarm codes are shown in the following table:

Alarm Code Description

DefRemoteCCM This MEP is not receiving CCMs from some other MEP in its configured list

DefErrorCCM: This MEP is receiving invalid CCMs

DefRDICCM The last CCM received by this MEP from some remote MEP contained the
RDI bit

DefXconCCM This MEP is receiving CCMs that could be from some other MA

In the implementation ZTE RNC, only alarm level higher than LOWESTALARMPRI would
be triggered.
The fault verification and path discovery function is also provided, user can perform
standard Loop Back and Link Trace test via OMCRs diagnose management view.

ITU-Y 1731
ITU-Y 1731 standard is a additional supplement for IEEE 802.3ah and EEE 802.1ag
standard which further described link performance test and fault monitoring method. ZTE
RNC supports the following ITU-Y 1731 diagnose test feature:

1. Bidirectional Ethernet delay test: MEP will sending and receiving DM frames
periodically to and from remote MEP to fulfill frame delay and jitter measurement.
2. Unidirectional Ethernet delay test: MEP will sending DM frames periodically to remote
MEP, remote MEP hence fulfill frame delay and jitter measurement.
For RNC only act as the customer edge equipment in management domain, so no AIS
message defined by ITU-Y 1731 will be produced by RNC. RNC can process received
AIS message created by upriver MIPs.

1-4

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

 Chapter 2
Preparations
License
None

Hardware Requirement
Hardware Requirement is shown inTable 2-1.

Table 2-1 Hardware Requirement

NE Requirement

RNC GIPI3 or GIPI4,GUIM

NodeB None

Optical switch

Software Requirement
Software Requirement is shown inTable 2-2.

Table 2-2 Software Requirement

NE Involved Version Requirement

UE NO None

NodeB YES V4.11.10.14 ZTE equipment

RNC YES V3.11.10.11 ZTE equipment

MSCS NO ZTE equipment

MGW NO ZTE equipment

SGSN NO ZTE equipment

GGSN NO

HLR NO

Topology
Topology is shown in.

2-1

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF22-03-009

2-2

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

 Chapter 3
Data configuration
SGSN/GGSN - ZTE
None

MSC/MGW - ZTE
None

HLR ZTE
None

RNC
1. We need to configure a real port for the Iub interface board first
l Sub interface NO: 0 (0 is real port)
l Unit NO: 15 (the slot number of GIPI3 )
l MAC Address: 00-19-c6-43-bf-1c (generate automatically)
Path: View-> > Configuration Management -> > RNC NE-> > RNC Ground
Resource Management-> > Transmission Configuration-> > IP Protocol
Configuration -> > Interface Configuration
Other parameters in this page are set as default, IP address can be configured freely.:

2. Configure the virtual port and assign a VLAN ID for Iub interface.
l Sub Interface NO:1(virtual port)
l VlAN ID:18

3-1

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF22-03-009

l IP address: 110.130.21.1
Path: View-> > Configuration Management -> > RNC NE-> > RNC Ground
Resource Management-> > Transmission Configuration-> > IP Protocol
Configuration -> > Interface Configuration

3. MD,MA and MEP parameters setting:

l MD Index: 1
l MD Name: SDR18 (it is globally unique, and different with MA name)
l MD Level: 0 (0 is the highest lever),
Path: View-> > Configuration Management -> > RNC NE-> > RNC Ground
Resource Management-> > Transmission Configuration-> > Connectivity Fault
Management -> > Connectivity Fault Management Maintenance Domain

3-2

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

 Chapter 3 Data configuration

l MD Index: 1
l MA Index: 1
l MA Name: SDR (globally unique)
l MA VLAN ID: 18 (the same with Iub interface VLAN ID configured in step2)
l CCM Period: 1s (default value)
Path: View-> > Configuration Management -> > RNC NE-> > RNC Ground
Resource Management-> > Transmission Configuration-> > Connectivity Fault
Management -> > Connectivity Fault Management Maintenance Domain > >
Connectivity Fault Management Maintenance Association

3-3

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF22-03-009

Create 2 MEP in the MA:

l Local MEP Index: 1
l Remote MEP Index:0 (when MEP type is local type ,remote mep index must be 0)
l MEP ID: 1 (Unique in MA)
l MEP Type: local mep
l Unit/Sunit/Local Port NO.: 15/1/1 (according to the iub interface board)
l Enable CCM Send or Not: enable
l Enable CCM Receive or Not: enable
l Priority: 7(default value)
Path: View-> > Configuration Management -> > RNC NE-> > RNC Ground
Resource Management-> > Transmission Configuration-> > Connectivity Fault
Management -> > Connectivity Fault Management Maintenance Domain > >
Connectivity Fault Management Maintenance Association-> > Connectivity
Fault Management Maintenance association End Point

l Local MEP Index: 1

l Remote MEP Index:2 (Unique in MA)
l MEP ID: 2
l MEP Type: remote mep
l MEP MAC: 00-15-EB-95-FC-2D (it is NodeB MAC address, can be checked on
NodeB side in 1.5.5)

Path: View-> > Configuration Management -> > RNC NE-> > RNC Ground
Resource Management-> > Transmission Configuration-> > Connectivity Fault

3-4

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

 Chapter 3 Data configuration

Management -> > Connectivity Fault Management Maintenance Domain > >
Connectivity Fault Management Maintenance Association-> > Connectivity
Fault Management Maintenance association End Point

NodeB
The NodeB is running normally before configure CFM parameters.
1. MD Parameters in table EthernetCfmMd of nodeb data
l MD NO.
l MD Index ID
l Used Physical Port: choose the Ethernet port no. which is set in Nodeb Ethernet
configuration already.
l MD Level: 0
l MD Name: SDR 18

2. MA Parameters in table EthernetCfmMa of nodeb data

l MD NO.
l MA NO.
l MA Index
l Used Ethernet Link: choose the Ethernet link No. which is set in Nodeb Ethernet
configuration already.

3-5

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF22-03-009

l VLAN ID: 18
l MA Name: SDR
l CCM Detective Duration: 1s

3. MEP Parameters in table EthernetCfmMp of nodeb data

l MA NO.
l MP NO.
l MP Index ID
l MEP Full NET NO.
l MEP Type; Local MEP should be the same with RNC remote MEP, Remote MEP
should be same with RNC local MEP
l Local MEP Level: 7 for local MEP
l Lowest Alarm Level: 2 for local MEP
l Associated Local MP Index: configured in remote MEP. The same with local MEP
Index ID.
l MAC Address of Remote MEP: 00-19-c6-43-bf-1c (should be same with the GIPI
MAC address set on RNC side in 1.5.4)
l Enable CCM Detective or Not: YES for local MEP, NO for remote MEP

4. Import data and check the parameters configured above in data view of EOMS

3-6

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

 Chapter 3 Data configuration

3-7

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF22-03-009

5. Check the MAC Address of NodeB:

Telnet on the CC board of NODEB, the password is zte. Input ./ushell command

Input pad 657 and FeInfo command to check the MAC address (00-15-eb-95-fc-2d).

3-8

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

 Chapter 3 Data configuration

3-9

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF22-03-009

This page intentionally left blank.

3-10

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

 Chapter 4
Testing
Table of Contents
Test Purpose ..............................................................................................................4-1
Steps for Test .............................................................................................................4-1
Expected Results .......................................................................................................4-5

4.1 Test Purpose

The purpose of this test case is to verify RNC CFM function is normal.
Related documents

ZTE UMTS IP UTRAN Feature Guide.doc

4.2 Steps for Test

Continuity Check
1. Disconnect the Ethernet cable of IUB from GIPI board.
2. Check the RNC Fault Management , CFM alarm is generated:

3. Plug in the cable again, and check that the CFM alarm will be recovered.

4-1

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF22-03-009

Loopback Test
1. Start the Loopback Test in the Test Management

Test type: Start CFM Test.

Function type: Loopback Test

MD Index Number, MA Index Number, Local MEP Index Number and Remote MEP
Index Number are configured according to the RNC CFM configuration.

4-2

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

 Chapter 4 Testing

Remote NodeB Type: MEP

Operation Type: Index Number
Send Packets Number and Time to Stop Receiving LBR can be set freely.

2. Stop the Loopback Test in the Test Management after a while.

Check the test result: local mep send 10 packets to remote mep, and received 10
packets, the packet loss rate is 0%, the test result is OK.

4-3

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF22-03-009

Linktrace Test
1. Start the Linktrace Test in the Test Management.

Test type: Start CFM Test

Function type: Linktrace Test

MD Index Number, MA Index Number, Local MEP Index Number and Remote MEP
Index Number are configured according to the RNC CFM configuration.
TTL and Time to Stop Receiving LBR can be set freely

4-4

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

 Chapter 4 Testing

2. Stop the Linktrace Test in the Test Management after a while.

Check the Linktrace Test: there is only one hop in the MA, and the next hop MAC
address is Nodeb MAC address. The test result is OK.

4.3 Expected Results

Continuity Check
After pull out the cable, DefRemoteCCM alarm can be found.

After plug in the cable, the alarm recovered.

4-5

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF22-03-009

Loopback Test
RNC can send and receive CCM message normally.

Linktrace Test
OMM can show the link trace normally.

4-6

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential

 Chapter 5
Counter List
None.

5-1

SJ-20120802112720-133|2012-08-03(R1.0) ZTE Proprietary and Confidential