2-Antenna Receive Diversity (GBSS16.0 - 01)

SingleRAN
SRAN12.0
Ethernet OAM Feature Parameter

Description
Issue 01
Date 2016-09-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2016-09-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
SingleRAN
Ethernet OAM Feature Parameter Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 2
1.3 Change History............................................................................................................................................................... 2
1.4 Differences Between Base Station Types....................................................................................................................... 3
2 Overview......................................................................................................................................... 4
2.1 Introduction.................................................................................................................................................................... 4
2.2 Benefits........................................................................................................................................................................... 4
2.3 Architecture.................................................................................................................................................................... 4
3 Ethernet OAM (IEEE 802.3ah)..................................................................................................... 6

3.1 Introduction.................................................................................................................................................................... 6
3.2 Principles........................................................................................................................................................................ 6
3.3 Application Scenarios.....................................................................................................................................................7
3.4 Technical Description..................................................................................................................................................... 8
4 Ethernet OAM (IEEE 802.1ag)................................................................................................... 12

4.1 Introduction.................................................................................................................................................................. 12
4.2 Principles...................................................................................................................................................................... 12
4.3 Application Scenarios...................................................................................................................................................14
4.4 Technical Description................................................................................................................................................... 14
5 Ethernet OAM (ITU-T Y.1731).................................................................................................. 16

5.1 Introduction.................................................................................................................................................................. 16
5.2 Principles...................................................................................................................................................................... 16
5.3 Application Scenarios...................................................................................................................................................16
5.4 Technical Description................................................................................................................................................... 17
6 Related Features...........................................................................................................................20
6.1 GBFD-118630 Ethernet OAM......................................................................................................................................20
6.2 WRFD-050425 Ethernet OAM.................................................................................................................................... 21
6.3 LOFD-003004 Ethernet OAM......................................................................................................................................22
6.4 TDLOFD-003004 Ethernet OAM................................................................................................................................ 23
7 Network Impact........................................................................................................................... 25
7.1 GBFD-118630 Ethernet OAM......................................................................................................................................25
Issue 01 (2016-09-30) Huawei Proprietary and Confidential ii

SingleRAN
7.2 WRFD-050425 Ethernet OAM.................................................................................................................................... 25

7.3 LOFD-003004/TDLOFD-003004 Ethernet OAM....................................................................................................... 26
8 Engineering Guidelines............................................................................................................. 27
8.1 When to Use................................................................................................................................................................. 27
8.2 Required Information................................................................................................................................................... 28
8.3 Planning........................................................................................................................................................................ 29
8.3.1 RF Planning............................................................................................................................................................... 29
8.3.2 Network Planning...................................................................................................................................................... 29
8.3.3 Hardware Planning.................................................................................................................................................... 29
8.4 Deployment of Ethernet OAM (IEEE 802.3ah) for GSM............................................................................................29
8.4.1 Requirements............................................................................................................................................................. 29
8.4.2 Data Preparation........................................................................................................................................................ 30
8.4.3 Precautions.................................................................................................................................................................32
8.4.4 Hardware Adjustment................................................................................................................................................32
8.4.5 Activation.................................................................................................................................................................. 32
8.4.6 Activation Observation..............................................................................................................................................33
8.4.7 Reconfiguration......................................................................................................................................................... 34
8.4.8 Deactivation...............................................................................................................................................................34
8.5 Deployment of Ethernet OAM (IEEE 802.3ah) for UMTS......................................................................................... 34
8.5.1 Requirements............................................................................................................................................................. 34
8.5.3 Precautions.................................................................................................................................................................36
8.5.5 Activation.................................................................................................................................................................. 36
8.5.8 Deactivation...............................................................................................................................................................38
8.6 Deployment of Ethernet OAM (IEEE 802.3ah) for LTE..............................................................................................38
8.6.1 Requirements............................................................................................................................................................. 38
8.6.3 Precautions.................................................................................................................................................................39
8.6.5 Activation.................................................................................................................................................................. 39
8.6.8 Deactivation...............................................................................................................................................................40
8.7 Deployment of Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731) for GSM.................................... 40
8.7.1 Requirements............................................................................................................................................................. 40
8.7.3 Precautions.................................................................................................................................................................47
8.7.5 Activation.................................................................................................................................................................. 47
Issue 01 (2016-09-30) Huawei Proprietary and Confidential iii

SingleRAN

8.7.8 Deactivation...............................................................................................................................................................51
8.8 Deployment of Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731) for UMTS..................................52
8.8.1 Requirements............................................................................................................................................................. 53
8.8.3 Precautions.................................................................................................................................................................58
8.8.5 Activation.................................................................................................................................................................. 58
8.8.8 Deactivation...............................................................................................................................................................61
8.9 Deployment of Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731) for LTE......................................61
8.9.1 Requirements............................................................................................................................................................. 62
8.9.3 Precautions.................................................................................................................................................................62
8.9.5 Activation.................................................................................................................................................................. 63
8.9.8 Deactivation...............................................................................................................................................................63
8.10 Performance Monitoring.............................................................................................................................................64
8.11 Parameter Optimization.............................................................................................................................................. 65
8.12 Possible Issues............................................................................................................................................................ 65
9 Parameters..................................................................................................................................... 67
10 Counters...................................................................................................................................... 89
11 Glossary....................................................................................................................................... 94
12 Reference Documents............................................................................................................... 95
Issue 01 (2016-09-30) Huawei Proprietary and Confidential iv

SingleRAN
Ethernet OAM Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes Ethernet Operations, Administration and Maintenance (OAM),
including its technical principles, related features, network impact, and engineering
guidelines.
Ethernet OAM is based on the IEEE 802.3ah, IEEE 802.1ag, and ITU-T Y.1731 protocols.
This document covers the following features:
l GBFD-118630 Ethernet OAM

l WRFD-050425 Ethernet OAM
l LOFD-003004 Ethernet OAM
l TDLOFD-003004 Ethernet OAM
NOTE
Unless otherwise specified, the following naming conventions are applied:

l "LTE" refers to LTE FDD and LTE TDD.
l "eNodeB" refers to LTE FDD eNodeB and LTE TDD eNodeB.
l "eRAN" refers to LTE FDD eRAN and LTE TDD eRAN.
In addition, the "L" and "T" in RAT acronyms refer to LTE FDD and LTE TDD, respectively.
Table 1-1 lists the Ethernet OAM supported by NEs of each mode.
Table 1-1 Ethernet OAM supported by NEs of each mode

Base NE Ethernet OAM Ethernet OAM Ethernet OAM
Station (IEEE 802.3ah) (IEEE 802.1ag) (ITU-T Y.1731)
Type
GSM base GBTS/eGBTS Supported Supported Supported

station
BSC Supported Supported Not supported
UMTS base NodeB Supported Supported Supported

station
Issue 01 (2016-09-30) Huawei Proprietary and Confidential 1

SingleRAN
Base NE Ethernet OAM Ethernet OAM Ethernet OAM

Station (IEEE 802.3ah) (IEEE 802.1ag) (ITU-T Y.1731)
Type
RNC Supported Supported Not supported
LTE base eNodeB Supported Supported Supported

station
Multimode Multimode Supported Supported Supported

base station base station
For definitions of base stations described in this document, see section "Base Station
Products" in SRAN Networking and Evolution Overview Feature Parameter Description.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein

l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier
version
SRAN12.1 01 (2017-03-08)
This issue does not include any changes.
SRAN12.1 Draft A (2016-12-30)

Draft A (2016-12-30) of SRAN12.1 introduces the following changes to Issue 01
(2016-09-30) of SRAN12.0.
Change Change Description Parameter Change

Type
Feature Added the descriptions of the FG2e board of the None

change base station controller.

SingleRAN
Change Change Description Parameter Change

Type
Editorial None None

change
1.4 Differences Between Base Station Types

Feature Support by Macro, Micro, and LampSite Base Stations
Feature ID Feature Supported by Supported Supported
Name Macro Base by Micro by
Stations Base LampSite
Stations Base
Stations
GBFD-118630 Ethernet OAM Yes No No
WRFD-050425 Ethernet OAM Yes Yes Yes
LOFD-003004 Ethernet OAM Yes Yes Yes
TDLOFD-003004 Ethernet OAM Yes No No
Function Implementation in Macro, Micro, and LampSite Base Stations

Function Difference
Ethernet OAM Micro base stations do not support Ethernet OAM (which is defined
in ITU-T Y.1731).

SingleRAN
Ethernet OAM Feature Parameter Description 2 Overview
2 Overview
2.1 Introduction
With the advent of Internet Protocol (IP) transformation in telecom operator networks,
Ethernet bearer networks are widely used. To guarantee the reliability and availability of
Ethernet services, the Ethernet OAM feature is introduced.
This feature provides detection, notification, verification, and locating functions for detectable
hard faults (such as link disconnection) or undetectable soft faults (such as damages in
memory bridges).
From this version onwards, Ethernet OAM supports three protocols: point-to-point IEEE
802.3ah, end-to-end IEEE 802.1ag, and end-to-end ITU-T Y.1731.
NOTE
Point-to-point Ethernet OAM IEEE 802.3ah: IEEE 802.3ah must be enabled for two pieces of
equipment that are directly connected and Ethernet switch equipment cannot be connected between these
two pieces of equipment.
End-to-end Ethernet OAM IEEE 802.1ag or ITU-T Y.1731: It can be enabled for two pieces of
equipment that are not directly connected, but they must have Layer 2 connectivity provided by Layer 2
switches between them.
2.2 Benefits
The Ethernet OAM feature provides the following benefits:
l Helps improve operators' capabilities of managing and maintaining the Ethernet.

l Guarantees network reliability.
l Reduces the operating expense (OPEX).
2.3 Architecture
The Ethernet OAM feature detects and reports the network status at the data link layer to
efficiently monitor and manage the Ethernet. Figure 2-1 shows the position of the Ethernet
OAM protocols in the OSI model.

SingleRAN
Ethernet OAM Feature Parameter Description 2 Overview
Figure 2-1 Position of Ethernet OAM protocols in the OSI model
Ethernet OAM protocols are functional between the Media Access Control (MAC) sublayer
of the Ethernet data link layer and the logical link control (LLC) layer. Therefore, other
protocol sublayers at the Ethernet data link layer and other OSI layers are not affected.

SingleRAN
Ethernet OAM Feature Parameter Description 3 Ethernet OAM (IEEE 802.3ah)
3 Ethernet OAM (IEEE 802.3ah)
3.1 Introduction
Ethernet OAM (IEEE 802.3ah) is a point-point Ethernet OAM protocol used to implement the
Ethernet in the First Mile (EFM) OAM function. With this function, the link status is
monitored effectively.
The EFM OAM function must be enabled for two pieces of equipment that are directly
connected during point-point Ethernet OAM services. The function detects faults on Ethernet
links by using the automatic discovery, fault detection, link monitoring, and remote loopback
mechanisms.
After Ethernet OAM (IEEE 802.3ah) is deployed between a base station (or base station
controller) and transmission equipment that is directly connected to the Ethernet interface,
OAM Protocol Data Units (PDUs) are exchanged between the local end and remote end to
detect the link status, as shown in Figure 3-1. However, the remote transmission equipment
must support IEEE 802.3ah.
Figure 3-1 Ethernet OAM (IEEE 802.3ah)
3.2 Principles
Ethernet OAM (IEEE 802.3ah) supports active and passive modes.
l In active mode, the local end sends negotiation packets to the peer end.
l In passive mode, the local end waits for negotiation packets from the peer end.

SingleRAN
It is recommended that Ethernet OAM (IEEE 802.3ah) work in active mode. In applications,
only when both ends at a point-to-point link work in passive mode, neither end initiates the
automatic discovery procedure. The automatic discovery procedure is also known as OAM
discovery. To implement OAM functions, automatic discovery must be enabled first. OAM
clients in different modes have different OAM support capabilities. For details, see Table 3-1.
Table 3-1 OAM client capabilities in different modes

Capability Active Mode Passive Mode
Initiating automatic discovery Yes No
Responding to automatic discovery Yes Yes

initiation
Sending Information OAM PDUs Yes Yes
Sending Event Notification OAM PDUs Yes Yes
Sending Variable Request OAM PDUs Yes No
Sending Variable Response OAM PDUs Yes Yes
Sending Loopback Control OAM PDUs Yes No
Responding to Loopback Control OAM Yes Yes

PDUs
Sending Organization Specific OAM Yes Yes

PDUs
3.3 Application Scenarios

The IEEE 802.3ah protocol requires that the local end and remote end are directly connected
during link detection. Figure 3-2 shows a network topology when Ethernet OAM (IEEE
802.3ah) is used. In this scenario, Ethernet links between the base station (or the base station
controller) and transmission equipment are managed using Ethernet OAM (IEEE 802.3ah).

SingleRAN
Figure 3-2 Network topology with Ethernet OAM (IEEE 802.3ah) enabled
3.4 Technical Description

The IEEE 802.3ah protocol defines four basic functions: automatic discovery, fault detection,
link monitoring, and remote loopback. Automatic discovery is a process of establishing and
interacting OAM sessions and is the prerequisite for other OAM functions. Link monitoring,
fault detection, and remote loopback are used to monitor network performance and locate link
failures.
Automatic Discovery
Automatic discovery is the first phase for the implementation of Ethernet OAM (IEEE
802.3ah). For example, if the radio equipment works in active mode and the transmission
equipment works in passive mode, the two ends exchange OAM PDUs to obtain their
respective OAM support capabilities, as shown in Figure 3-3.
Figure 3-3 Automatic discovery procedure
Fault Detection
l When the local end is faulty, the local OAM client notifies the remote OAM client of the
fault by sending an OAM PDU that contains the fault information.
l When the remote end is faulty, the remote OAM client notifies the local OAM client of
the fault by sending an OAM PDU that contains the fault information.

SingleRAN
Link Monitoring
Link monitoring is used to monitor bit errors, such as errored frames and errored signals on a
link. When the bit error rate (BER) exceeds a specified threshold, the local OAM client
notifies the remote OAM client of the corresponding bit error event by sending an Event
Notification OAM PDU. Then, the remote OAM client reports the link fault to the local OAM
client.
To measure the performance from different perspectives, the link monitoring function is
divided into errored frame event monitoring, errored frame seconds event monitoring, and
errored frame period event monitoring.
l Errored frame event monitoring: The errored frame event monitoring period refers to the
period in which errored frames are measured once. In this period, the number of detected
errored frames is greater than or equal to the specified errored frame event threshold.
The related parameters in GSM, UMTS, and LTE modes are as follows:
NE Parameter Name Parameter ID
BSC/RNC Err Frame Event Prid[s] ERFAMEventPrid
Err Frame Event Para ERFAMEventPara
GBTS Err Frame Event Prid[s] ERFAMEventPrid
Err Frame Event Para ERFAMEventPara
eGBTS/NodeB/eNodeB Error Frame Event ERRFRMEVTPRD

Duration
Error Frame Event ERRFRMEVTTHD

Threshold
NOTE
l The GBTS and eGBTS use different MML commands, and therefore they may use different
parameter IDs and names.
l Unless otherwise specified, "base station controller" in this document is a generic term for
GSM and UMTS modes.
l Errored frame seconds event monitoring: In an errored frame seconds summary event
period, the number of detected errored frame seconds is greater than or equal to the
specified errored frame seconds summary event threshold. An errored frame seconds
event indicates that at least one errored frame is detected in a second. The related
parameters in GSM, UMTS, and LTE modes are as follows:
BSC/RNC Err Frame Sec Event Prid[s] ERFAMSCDEventPrid
Err Frame Sec Event Para[s] ERFAMSCDEventPara
GBTS Err Frame Sec Event Prid[s] ERFAMSCDEventPrid
Err Frame Sec Event Para[s] ERFAMSCDEventPara

SingleRAN
eGBTS/NodeB/ Error Frame Seconds ERRFRMSCDEVTPRD

eNodeB Summary Event Duration
Error Frame Seconds ERRFRMSCDEVTTHD

Summary Event Threshold
l Errored frame period event monitoring: In an errored frame cycle event monitoring
period, the number of detected received errored frames is greater than or equal to the
specified threshold for the received errored frame cycle events. The related parameters in
GSM, UMTS, and LTE modes are as follows:
NOTE
Among all base stations and base station controllers in GSM, UMTS, and LTE modes, only the
BSC/RNC and GBTS support the errored frame period event monitoring function.
BSC/RNC Err Frame Cyc Event Prid ERFAMPRDEventPrid
Err Frame Cyc Event Para ERFAMPRDEventPara
GBTS Err Frame Cyc Event Prid ERFAMPRDEventPrid
Err Frame Cyc Event Para ERFAMPRDEventPara
Remote Loopback
In a remote loopback, the local OAM client sends packets to the remote OAM client, and the
remote OAM client loops back packets other than non-OAM PDUs. The remote loopback
function can be used to locate link faults and check link quality.
The local OAM client sends a Loopback Control OAM PDU to the remote OAM client,
instructing it to enter the loopback state. As shown in Figure 3-4, after the remote OAM
client enters the loopback state, the local OAM client sends packets to the remote OAM client
and then calculates the packet loss rate and other KPIs on the current link based on the
number of the sent and received packets.
Figure 3-4 Remote loopback
Only the port in active mode can initiate a remote loopback. The remote loopback function
can be enabled on a port only if both the following conditions are met:

SingleRAN
l The port works in active mode.

l The port and the peer port are detectable.
Assuming that the local OAM client is radio equipment and the remote OAM client is
transmission equipment, the remote loopback function is implemented as follows:
1. The radio equipment sends a Loopback Control OAMPDU with the Enable OAM
Remote Loopback command to the transmission equipment.
2. Upon receiving the Loopback Control OAMPDU, the transmission equipment responds
with an Information OAMPDU with updated state message to the radio equipment and
enters the loopback state.
3. The radio equipment enters the loopback state if it receives the Information OAMPDU
with updated state from the transmission equipment within a specified period. The radio
equipment sends the Loopback Control OAMPDU with the Enable OAM Remote
Loopback command again if it has not received the Information OAMPDU with updated
state from the transmission equipment within the specified period. The radio equipment
can send the command three consecutive times at most.
4. If the radio equipment needs to terminate the remote loopback, it sends a Loopback
Control OAMPDU with the Disable OAM Remote Loopback command to the
transmission equipment. Upon receiving the command, the transmission equipment exits
the loopback state.

SingleRAN
Ethernet OAM Feature Parameter Description 4 Ethernet OAM (IEEE 802.1ag)
4 Ethernet OAM (IEEE 802.1ag)
4.1 Introduction
The Ethernet OAM (IEEE 802.1ag) is an end-to-end Ethernet OAM protocol used to
implement the Connectivity Fault Management (CFM) function. The CFM function is a
network-level Ethernet OAM technology and comprises continuity check, loopback, and
linktrace functions. With the CFM function, the continuity faults on the entire network can be
detected and located.
If the base station or base station controller detects Ethernet faults or undesirable network
performance using Ethernet OAM (IEEE 802.1ag), it initiates rerouting, port switchover, or
board switchover accordingly, to ensure normal connection of Ethernet links.
4.2 Principles
Ethernet OAM (IEEE 802.1ag) reports the status of the data link layer and therefore
effectively monitors and manages the network. To enable Ethernet OAM (IEEE 802.1ag), the
local end and remote end on the network must support IEEE 802.1ag.
To implement end-to-end Ethernet link maintenance and fault detection and isolation,
Ethernet OAM (IEEE 802.1ag) defines Maintenance Domain (MD), Maintenance Association
(MA), Maintenance Point (MP), Maintenance End Point (MEP), and Maintenance
Intermediate Point (MIP).
Ethernet OAM (IEEE 802.1ag) implements the service-based end-to-end detection. In
addition, it detects the network segments along the same service flow one by one.
l MD
The maintenance domain name is specified by the MDNAME parameter and denotes a
network or a part of a network in which the CFM is implemented. An MD is usually
managed by an Internet Service Provider (ISP) or an operator.
MDs can be managed on a per level basis. The level of an MD is specified by the Level
parameter. A high-level MD can span low-level MDs, but a low-level MD cannot span
high-level MDs. This level-based MD management allows the same service flow to be
maintained segment by segment and also applies to different service flows.
Ethernet OAM (IEEE 802.1ag) supports eight MD levels, ranging from 0 to 7. Level 7 is
the highest MD level, and level 0 is the lowest.

SingleRAN
l MA
An MD can be divided into one or more MAs. The continuity of each MA can be
checked using the CFM function.
In networks of operators, one Virtual Local Access Network (VLAN) generally
corresponds to one service instance and one MA. Therefore, the continuity check of
service instances can be performed on a per MA basis.
l MEP
MEPs are end points of MAs. In an MA, MEPs on the radio equipment that supports
IEEE 802.1ag are defined as local MEPs and those on other equipment are defined as
remote MEPs.
l MIP
MIPs are intermediate points of MAs.
All OAM operations are initiated by MEPs. MIPs do not actively initiate any OAM
operation or send any OAM packets.
Figure 4-1 shows the relationship among MD, MA, MEP, MIP, and VLAN. The local and
remote ends are configured in the same MD. The MD is divided into two MAs, MA 1 and
MA 2. MA 1 contains MEPID 1 configured on the Lport1 and MEPID 2 configured on the
Rport2. MA 2 contains MEPID 1 configured on the LPort2 and MEPID 2 configured on the
RPort1. The IDs of MEPs in different MAs can be the same.
In this example, LPort1 and LPort2 serve as local MEPs, and the RPort1 and RPort2 serve as
remote MEPs.
Figure 4-1 Relationship among MD, MA, MEP, MIP, and VLAN
NOTE
The radio equipment can work as an MEP but cannot work as an MIP.
The MEPs at different MD levels process OAM packets as follows:
l MEPs transparently transmit the OAM packets from a higher MD level.

l MEPs discard the OAM packets from a lower MD level.
l MEPs respond to or terminate the OAM packets from the same MD level based on the
OAM packet type.

SingleRAN

Figure 4-2 shows a network topology when Ethernet OAM (IEEE 802.1ag) is used. Ethernet
OAM (IEEE 802.1ag) is deployed between GBTS/NodeB/eNodeB/eGBTS and transmission
equipment, and between BSC/RNC and transmission equipment.
Figure 4-2 Network topology with Ethernet OAM (IEEE 802.1ag) enabled

Ethernet OAM (IEEE 802.1ag) implements end-to-end Ethernet maintenance and detection
using the following functions:
l Continuity check (CC)
CC is one of basic functions provided by Ethernet OAM (IEEE 802.1ag) and can be used
to check the continuity of Ethernet links between MEPs on two pieces of Ethernet
equipment.
After this function is enabled, each MEP in an MD periodically sends continuity check
messages (CCMs) and all MEPs in the same MD can receive the CCM packets.
However, these MEPs do not need to respond to the received CC packets. After
receiving a CCM packet from the remote MEP, the local MEP starts to measure the
number of periods of sending CCM packets. Within three consecutive periods (The
period is the same as the period of sending CCM packets from the remote MEP. The
local MEP uses the same period of sending CCM packets as the remote MEP), if the
local MEP does not receive any CCM packet from the remote MEP, the local MEP
determines that a continuity fault occurs between both ends.
l Loopback (LB)
LB is used to detect the bidirectional continuity between the local end and remote end.
The local MEP sends a Loopback Message which contains the MAC address or MEP ID
of the destination MP (MEP or MIP) and meanwhile starts a timer.
– If the destination MP responds with a Loopback Return message to the local MEP
after receiving the Loopback Message, the loopback is successful.
– If the local MEP does not receive the Loopback Return message from the
destination MP before the timer specified by the local MEP expires, the loopback
fails.
The LB is similar to the Ping operation and therefore is also called MAC PING.
l Linktrace (LT)
LT is used to retrieve the MP adjacency and locate faults. The local MEP sends a Link
Trace Message which contains the MAC address or MEP ID of the destination MEP and
meanwhile starts a timer. All MIPs in the same MD as the local MEP on the link receive
the Link Trace Message and then forward the message to the destination MEP. Upon

SingleRAN
receiving the Link Trace Message, the destination MEP responds with a Link Trace
Reply message to the local MEP.
– If the destination MEP terminates the Link Trace Message upon receiving it and
returns a Link Trace Reply to the local MEP, the link trace is successful.
– If the local MEP does not receive the Link Trace Reply message from the
destination MEP before the timer specified by the local MEP expires, the link trace
fails.
NOTE
The LT function cannot be enabled for links between the local MEP and MIPs.
In addition, the Link Trace Reply message contains the Time to Live (TTL) parameter
which specifies the position of the MP that responds with the message on the tested link.
LT is similar to TraceRoute and therefore is also called MAC TRACE.

SingleRAN
Ethernet OAM Feature Parameter Description 5 Ethernet OAM (ITU-T Y.1731)
5 Ethernet OAM (ITU-T Y.1731)
5.1 Introduction
Ethernet OAM (ITU-T Y.1731) is an enhancement of Ethernet OAM (IEEE 802.1ag). In
addition to the CFM function specified by IEEE 802.1ag, Ethernet OAM (ITU-T Y.1731)
implements the Performance Management function. The Performance Management function
allows the base station to perform single-ended Ethernet Loss Measurement (ETH-LM), two-
way Ethernet Delay Measurement (ETH-DM), and delay variation measurement.
Ethernet OAM (TU-T Y.1731) is defined by ITU-T Y.1731 (2008). Ethernet OAM (ITU-T Y.
1731) is supported only on the base station side.
5.2 Principles
The working principle for Ethernet OAM (ITU-T Y.1731) is similar to that for Ethernet OAM
(IEEE 802.1ag). For details, see section 4.2 Principles. The only difference is as follows:
To simplify the implementation, Ethernet OAM (ITU-T Y.1731) incorporates the following
changes:
l Combines MD and MA into a Maintenance Entity Group (MEG).
l Replaces the MA ID with MEG ID.
l Replaces MD level with MEG Level.
The definitions of MEPs, MIPs are the same in Ethernet OAM (ITU-T Y.1731) and Ethernet
OAM (IEEE 802.1ag).

Figure 5-1 shows a network topology when Ethernet OAM (ITU-T Y.1731) is used. Ethernet
OAM (ITU-T Y.1731) is deployed between a base station and transmission equipment and
both ends must support ITU-T Y.1731.

SingleRAN
Figure 5-1 Network topology with Ethernet OAM (ITU-T Y.1731) enabled

Ethernet OAM (ITU-T Y.1731) inherits the CFM function of Ethernet OAM (IEEE 802.1ag).
For details about the CFM function, see section 4.4 Technical Description. This section
describes the Performance Management function of Ethernet OAM (ITU-T Y.1731), which is
used for single-ended ETH-LM, two-way ETH-DM, and delay variation measurement.
Single-ended Ethernet Loss Measurement (ETH-LM)

Single-ended ETH-LM is used for on-demand OAM. LMM and LMR messages contain
values of counters for frame loss measurements.
Each MEP on the base station side can measure the following items:
l Local-end frame loss: loss of service frames in the downlink

l Remote-end frame loss: loss of service frames in the uplink
During a single-ended ETH-LM, an MEP on the base station side sends an LMM request
message to its peer MEP on the transmission equipment and receives an LMR message from
its peer MEP. If the LMM request message indicates that the value of the local counter TxFCf
is TxFCf[tc], the transmission equipment responds with an LMR message, as shown in
Figure 5-2. An LMM message contains the counter values as described in Table 5-1.
Figure 5-2 Single-ended ETH-LM

SingleRAN
Table 5-1 Counters for single-ended ETH-LM

Counter Description
TxFCf Local counter at the time of LMM message transmission
RxFCf Remote counter at the time of LMM message reception
TxFCb Remote counter at the time of LMR message transmission
RxFCl Local counter RxFCl at the time of LMR message reception
Upon receiving the LMR message, the base station uses the following values contained in the
message for local- and remote-end loss measurements:
l The respective values of the TxFCf, RxFCf, and TxFCb counters are TxFCf[tc],
RxFCf[tc], and TxFCb[tc] when the base station receives the LMR message. In this
message, the value of the local counter RxFCl is RxFCl[tc].
NOTE
The "tc" in the RxFCl[tc] indicates the time when the base station receives the current LMR message.
l The respective values of the TxFCf, RxFCf, and TxFCb counters are TxFCf[tp],
RxFCf[tp], and TxFCb[tp] when the base station receives the previous LMR message. In
this message, the value of the local counter RxFCl is RxFCl[tp].
NOTE
The "tp" in the RxFCl[tp] indicates the time when the base station receives the previous LMR message.
Based on the preceding values carried in LMR messages, the remote-end frame loss (in the
uplink) is calculated using the following formula:
Remote-end frame loss = (TxFCf[tc] – TxFCf[tp]) – (RxFCf[tc] – RxFCf[tp])
The local-end frame loss (in the downlink) is calculated using the following formula:
Local-end frame loss = (TxFCb[tc] – TxFCb[tp]) – (RxFCl[tc] – RxFCl[tp])
Two-Way ETH-DM
In two-way ETH-DM, if the local MEP sends a DMM frame with the TxTimeStampf value to
the remote MEP, and the remote MEP delays responding with a DMR frame, the delay will be
used as the delay for the entire L2 network. Figure 5-3 shows the detailed message exchanges
between the local MEP and remote MEP. The counters for ETH-DM are described in Table
5-2.
Frame delay = (RxTimeb – TxTimeStampf) – (TxTimeStampb – RxTimeStampf)

SingleRAN
Figure 5-3 Message exchange for two-way ETH-DM
Table 5-2 Counters for two-way ETH-DM

Counter Description
TxTimeStampf Local timestamp at the time of DMM

transmission from the local MEP
RxTimeStampf Local timestamp at the time of DMM

reception by the remote MEP
TxTimeStampb Local timestamp at the time of DMR

transmission from the remote MEP
RxTimeb Local timestamp at the time of DMR

reception by the local MEP
The frame delay variation can be calculated using the following formula:
Frame delay variation = Frame delay[tc] – Frame delay[tp]
NOTE
The "tc" indicates the value of the current frame delay, and the "tp" indicates the value of the previous
frame delay on the base station side.

SingleRAN
Ethernet OAM Feature Parameter Description 6 Related Features
6 Related Features
6.1 GBFD-118630 Ethernet OAM

Prerequisite Features
Feature ID Feature Name Description
GBFD-118601 Abis over IP N/A
GBFD-118602 A over IP N/A
GBFD-118603 Gb over IP N/A
Mutually Exclusive Features

Function Name Description
Ethernet OAM (IEEE 802.1ag) Ethernet OAM (IEEE 802.1ag) is mutually exclusive
with Ethernet OAM (ITU-T Y.1731). This implies that
Ethernet OAM (ITU-T Y.1731) Ethernet OAM (IEEE 802.1ag) and Ethernet OAM
(ITU-T Y.1731) cannot be enabled simultaneously on a
base station.

SingleRAN
Impacted Features
MRFD-210103 Link Aggregation l Ethernet trunk ports do not

support Ethernet OAM
(IEEE 802.3ah), but Ethernet
trunk member ports support
Ethernet OAM (IEEE
802.3ah).
l Ethernet trunk ports support
Ethernet OAM (ITU-T Y.
1731), but Ethernet trunk
member ports do not support
1731).
l When Ethernet OAM (ITU-T
Y.1731) is enabled for
Ethernet trunk ports, single-
end packet loss detection is
not supported.
6.2 WRFD-050425 Ethernet OAM

WRFD-050402 IP Transmission Introduction N/A

on Iub Interface

base station.

SingleRAN
Impacted Features
MRFD-210103 Link Aggregation l Ethernet trunk ports do not

support Ethernet OAM
Ethernet OAM (IEEE
802.3ah).
1731).
not supported.
6.3 LOFD-003004 Ethernet OAM

None

base station.

SingleRAN
Impacted Features
LOFD-003008 Ethernet Link Aggregation l Ethernet trunk ports do not

(IEEE 802.3ad) support Ethernet OAM
Ethernet OAM (IEEE
802.3ah).
1731).
not supported.
6.4 TDLOFD-003004 Ethernet OAM

None

base station.

SingleRAN
Impacted Features
Feature ID Feature Name Impact
TDLOFD-003008 Ethernet Link Aggregation l Ethernet trunk ports do not

(IEEE 802.3ad) support Ethernet OAM
Ethernet OAM (IEEE
802.3ah).
1731).
not supported.

SingleRAN
Ethernet OAM Feature Parameter Description 7 Network Impact
7 Network Impact
7.1 GBFD-118630 Ethernet OAM

System Capacity
No impact.
Network Performance
Ethernet OAM protocols are slow protocols and therefore can provide low data rate functions,
such as the ping function. In addition, Ethernet OAM protocols occupy low bandwidth and
therefore do not affect the data flow of other services. If the CCM function is enabled, packets
must be sent at an interval of at least one second because sending packets at a very short
interval affects the performance of transport networks.
When the remote loopback function provided by Ethernet OAM (IEEE 802.3ah) is enabled,
services carried on a base station are interrupted.
7.2 WRFD-050425 Ethernet OAM

System Capacity
No impact.
Network Performance

SingleRAN
Ethernet OAM Feature Parameter Description 7 Network Impact
7.3 LOFD-003004/TDLOFD-003004 Ethernet OAM

System Capacity
No impact
Network Performance

SingleRAN
Ethernet OAM Feature Parameter Description 8 Engineering Guidelines
8 Engineering Guidelines
8.1 When to Use

Before Ethernet OAM is enabled, the following conditions must be met:
l Both the base station or base station controller and the transport network are carried on
an L2 Ethernet.
l The transmission equipment supports Ethernet OAM.
Ethernet OAM (IEEE 802.3ah) is an effective link monitoring and fault detection mechanism
during point-to-point Ethernet OAM (only for the base station side). It is recommended that
Ethernet OAM (IEEE 802.3ah) be deployed for a base station or base station controller and
adjacent transmission equipment that supports IEEE.802.3ah.
Ethernet OAM (IEEE 802.1ag) is used to detect and maintain the continuity of end-to-end
Ethernet links. This feature implements service-based end-to-end continuity check per MD
and manages the network segments along the same service flow one by one. In addition, this
feature provides link detection and route interlock functions. It is recommended that Ethernet
OAM (IEEE 802.1ag) be deployed for a base station or base station controller and
transmission equipment that supports IEEE 802.1ag.
If frame loss and delay variation measurements are required for end-to-end Ethernet links,
you are advised to deploy Ethernet OAM (ITU-T Y.1731).
In base station co-transmission scenarios, Ethernet OAM is deployed only for a base station
that directly is connected to the transport network. Ethernet OAM is deployed only for a mode
of a base station if multiple modes of the base station are directly connected to the transport
network. Therefore, engineering guidelines for Ethernet OAM are described per base station
mode.

SingleRAN
NOTE
The GBTS and eGBTS use different MML commands, and therefore they may use different parameter
IDs and names.
Unless otherwise specified, "base station controller" in this document is a generic term for GSM and
UMTS modes.
l eGBTS refers to a base station deployed with UMPT_G.
l NodeB refers to a base station deployed with WMPT or UMPT_U.
l eNodeB refers to a base station deployed with LMPT or UMPT_L.
l Co-MPT multimode base station refers to a base station deployed with UMPT_GU, UMPT_GL,
UMPT_UL, or UMPT_GUL, and it functionally corresponds to any combination of eGBTS, NodeB,
and eNodeB. For example, Co-MPT multimode base station deployed with UMPT_GU functionally
corresponds to the combination of eGBTS and NodeB.
l Separate-MPT multimode base station refers to a base station on which different modes use different
main control boards. For example, base stations deployed with GTMU and WMPT are called
separate-MPT GSM/UMTS dual-mode base station.
8.2 Required Information

To deploy Ethernet OAM, collect the following information:
l Whether the transmission equipment supports Ethernet OAM

l The IEEE 802.1ag version (Draft 7 or standard version) supported by the transmission
equipment during Ethernet OAM (IEEE 802.1ag) deployment
l Whether the transmission equipment supports ITU-T Y.1731 (2008) during Ethernet
OAM (ITU-T Y.1731) deployment
The protocol version supported by the transmission equipment must be the same as that
supported by the radio equipment.
The following table describes the versions for IEEE 802.1ag and ITU-T Y.1731 protocols
supported by the radio equipment.
Protocol GBTS/NodeB/eNodeB/eGBTS BSC/RNC
IEEE 802.1ag From GBSS9.0/RAN9.0 to The base station controller

NOTE GBSS13.0/RAN13.0, the base supports both the Draft 7
IEEE 802.1ag is station supports only IEEE 802.1ag and standard version.
incompatible with its (Draft 7). From GBSS14.0/
draft version or EEE RAN14.0/eRAN3.0/SRAN7.0, the
802.1ag (2007).
base station supports only the
Therefore, both ends
must use the same standard version.
protocol version.
ITU-T Y.1731 The base station supports ITU-T Y. The base station controller
1731 (2008). does not support ITU-T Y.
1731 (2008).
When deploying Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731), plan the
following data for the base station (or base station controller) and transmission equipment:

SingleRAN
l MD: The MD is invalid during Ethernet OAM (ITU-T Y.1731) deployment.

l MA: The MA is replaced with the MEG ID during Ethernet OAM (ITU-T Y.1731)
deployment.
l MEP or RMEP
l VLAN
8.3 Planning
8.3.1 RF Planning
N/A
8.3.2 Network Planning

Ethernet OAM is deployed when IP networking is used.
8.3.3 Hardware Planning

None
8.4 Deployment of Ethernet OAM (IEEE 802.3ah) for GSM
8.4.1 Requirements
Hardware
The following boards support Ethernet OAM (IEEE 802.3ah) when they are configured with
Ethernet ports.
NE IEEE 802.3ah
BSC FG2a/FG2c/FG2d/FG2e/GOUa/GOUc/GOUd/EXOUa/
EXOUb
GBTS GTMUb/GTMUc/UTRP2/UTRP9/UTRPc
eGBTS UMPT/GTMUb/GTMUc
Transmission Equipment
Protocol Transmission Equipment
IEEE 802.3ah The transmission equipment supports Ethernet OAM (IEEE

802.3ah).
License

SingleRAN
None
8.4.2 Data Preparation

Table 8-1 and Table 8-2 list the data to prepare before activating Ethernet OAM (IEEE
802.3ah) on the BSC and GBTS, respectively. The data to prepare before activating Ethernet
OAM (IEEE 802.3ah) on the eGBTS side is the same as that on the NodeB side. For details,
see Table 8-3.
Table 8-1 Data to prepare before activating Ethernet OAM (IEEE 802.3ah) on the BSC side
MO Parameter Name Parameter Setting Data Source
ID Notes
EFMAH Subrack No. SRN -- Network plan

(negotiation not
required)
Slot No. SN -- Network plan

(negotiation not
required)
Port No. PN -- Network plan

(negotiation not
required)
PDU Send Prid[ms] PDUPrid -- Network plan

(negotiation not
required)
PDU Pkt Len[Byte] PDUSize -- Network plan

(negotiation not
required)
Err Frame Event ERFAMEvent -- Network plan

Prid[s] Prid (negotiation not
required)
Err Frame Event ERFAMEvent -- Network plan

Para Para (negotiation not
required)
Err Frame Cyc ERFAMPRD -- Network plan

Event Prid EventPrid (negotiation not
required)
Err Frame Cyc ERFAMPRD -- Network plan

Event Para EventPara (negotiation not
required)
Err Frame Sec ERFAMSCD -- Network plan

Event Prid[s] EventPrid (negotiation not
required)

SingleRAN
MO Parameter Name Parameter Setting Data Source

ID Notes
Err Frame Sec ERFAMSCD -- Network plan

Event Para[s] EventPara (negotiation not
required)
NOTE
"--" indicates no setting notes are provided.
Table 8-2 Data to prepare before activating Ethernet OAM (IEEE 802.3ah) on the GBTS side
MO Parameter Parameter ID Setting Data Source
Name Notes
BTSETHOAMA PDU Send PDUPrid -- Network plan

H Period (negotiation not
required)
PDU Packet PDUSize -- Network plan

Len (negotiation not
required)
Err Frame ERFAMEventP -- Network plan

Event Prid rid (negotiation not
required)
Err Frame ERFAMEventP -- Network plan

Event Para ara (negotiation not
required)
Err Frame Cyc ERFAMPRDEv -- Network plan

Event Prid entPrid (negotiation not
required)
Err Frame Cyc ERFAMPRDEv -- Network plan

Event Para entPara (negotiation not
required)
Err Frame Sec EERFAMSCD -- Network plan

Event Prid EventPrid (negotiation not
required)
Err Frame Sec ERFAMSCDEv -- Network plan

Event Para entPara (negotiation not
required)
NOTE
"--" indicates no setting notes are provided.

SingleRAN
8.4.3 Precautions
None
8.4.4 Hardware Adjustment

None
8.4.5 Activation
This section uses the scenario shown in Figure 3-2 as an example to describe how to activate
Ethernet OAM (IEEE802.3ah) using the MML and CME GUI.
NOTE
l To enable Ethernet OAM (IEEE 802.3ah) on the BSC side, you should also enable it on the
transmission equipment.
l To enable Ethernet OAM (IEEE 802.3ah) on the GBTS side, you should also enable it on the
Using MML Commands

On the BSC side
To activate Ethernet OAM (IEEE 802.3ah) on the BSC side, run the ACT EFMAH command
with the following parameters set to appropriate values:
1. PDUPRID: This parameter specifies the fault detection period based on the IEEE
802.3ah protocol.
2. PDUSize: This parameter specifies the length of an OAM PDU packet supported by
Ethernet OAM (IEEE 802.3ah).
3. Set the following parameters related to the time windows and thresholds for links
defined in IEEE 802.3ah:
l Err Frame Event Prid[s]
l Err Frame Event Para
l Err Frame Cyc Event Prid
l Err Frame Cyc Event Para
l Err Frame Sec Event Prid[s]
l Err Frame Sec Event Para[s]
On the GBTS side
To activate Ethernet OAM (IEEE 802.3ah) on the GBTS side, run the ACT
BTSETHOAMAH command with the following parameters set to appropriate values:
l PDUPRID: This parameter specifies the fault detection period based on the IEEE
802.3ah protocol.
l PDUSIZE: This parameter specifies the length of an OAM PDU packet supported by
l Set the following parameters related to the time windows and thresholds for links
l Err Frame Event Prid

SingleRAN
l Err Frame Event Para

l Err Frame Cyc Event Prid
l Err Frame Cyc Event Para
l Err Frame Sec Event Prid
l Err Frame Sec Event Para
On the eGBTS side
The procedure for activating Ethernet OAM (IEEE 802.3ah) using MML commands on the
eGBTS side is the same as that on the NodeB side. For details, see "On the NodeB side" in
"Using MML Commands" in section 8.5.5 Activation.
MML Command Examples

On the BSC side
//Activating the EFM OAM function
ACT EFMAH: SRN=0, SN=18, PN=0;
On the GBTS side

//Activating the EFM OAM function
ACT BTSETHOAMAH: IDTYPE=BYID, BTSID=7, PN=0;
On the eGBTS side

The MML command examples for activating Ethernet OAM (IEEE 802.3ah) on the eGBTS
side are the same as those on the NodeB side. For details, see "On the NodeB side" in "MML
Command Examples" in section 8.5.5 Activation.
Using the CME

The BSC, GBTS, and eGBTS support using CME single configuration to activate Ethernet
OAM (IEEE 802.3ah). Neither the BSC nor GBTS supports using CME batch configuration
to activate Ethernet OAM (IEEE 802.3ah), but the eGBTS does. For details, see "Using the
CME" in section 8.6.5 Activation.
8.4.6 Activation Observation

Using MML Commands
On the BSC side
Run the STR EFMLOOPTST command. Then, run the DSP EFMLOOPTST command to
query the value of Information of ETHOMA remote loopback. If the value is EthOam 3ah
Detect Status, the Ethernet OAM (IEEE 802.3ah) is enabled on a port.
On the GBTS side
Run the LST BTSETHOAMAH command to check whether the Ethernet OAM (IEEE
802.3ah) has been configured.
On the eGBTS side
The activation observation using MML commands on the eGBTS side is the same as that on
the NodeB side. For details, see "On the NodeB side" in section 8.5.6 Activation
Observation.

SingleRAN
8.4.7 Reconfiguration
None
8.4.8 Deactivation
Using MML Commands

On the BSC side
Run the DEA EFMAH command to deactivate Ethernet OAM (IEEE 802.3ah) on a port
configured with EFM OAM.
On the GBTS side
Run the DEA BTSETHOAMAH command to deactivate Ethernet OAM (IEEE 802.3ah) on
a port configured with EFM OAM.
On the eGBTS side
The procedure for deactivating Ethernet OAM (IEEE 802.3ah) using MML commands on the
eGBTS side is the same as that on the NodeB side. For details, see "On the NodeB side" in
"Using MML Commands" in section 8.5.8 Deactivation.

On the BSC side
//Deactivating the EFM OAM function on the FG2a board
DEA EFMAH: SRN=0,SN=18,PN=0;
On the GBTS side

//Deactivating the EFM OAM function
DEA BTSETHOAMAH: IDTYPE=BYID, BTSID=7, PN=0;
On the eGBTS side
The MML command examples for deactivating Ethernet OAM (IEEE 802.3ah) on the eGBTS
Command Examples" in section 8.5.8 Deactivation.
8.5 Deployment of Ethernet OAM (IEEE 802.3ah) for

UMTS
8.5.1 Requirements
Hardware
Ethernet ports.

SingleRAN
NE IEEE 802.3ah
RNC FG2a/FG2c/FG2d/FG2e/GOUa/GOUc/GOUd/EXOUa/
EXOUb
NodeB WMPT/UMPT/UTRP2/UTPR9/UTRPc
Protocol Requirement for Transmission Equipment
IEEE 802.3ah The transmission equipment supports Ethernet OAM

(IEEE 802.3ah).
License
Feature ID Feature License License Control NE Sales Unit

Name Control Item
Item ID
WRFD-05042 Ethernet LQW9ETO Ethernet OAM NodeB Per NodeB

5 OAM AM01 (per NodeB)

The data to prepare before activating this feature on the RNC side is the same as that on the
BSC side. For details, see Table 8-1. Table 8-3 lists the data to prepare before activating this
feature on the NodeB side.
Table 8-3 Data to prepare before activating Ethernet OAM (IEEE 802.3ah) on the NodeB side
Name Notes
ETHOAM3AH Work Mode WORKMODE -- Network plan

(negotiation not
required)
Detection DTPRD -- Network plan

Period (negotiation not
required)
PDU Size PDUSIZE -- Network plan

(negotiation not
required)

SingleRAN

Name Notes
Error Frame ERRFRMEVTPRD -- Network plan

Event Duration (negotiation not
required)
Error Frame ERRFRMEVTTHD -- Network plan

Event (negotiation not
Threshold required)
Error Frame ERRFRMSCDEVT -- Network plan

Seconds PRD (negotiation not
Summary required)
Event Duration
Error Frame ERRFRMSCDEVT -- Network plan

Seconds THD (negotiation not
Summary required)
Event
Threshold
8.5.3 Precautions
None

None
8.5.5 Activation
NOTE
l To enable Ethernet OAM (IEEE802.3ah) on the RNC side, you should also enable it on the
l To enable Ethernet OAM (IEEE802.3ah) on the NodeB side, you should also enable it on the
Using MML Commands

On the RNC side
RNC side is the same as that on the BSC side. For details, see "On the BSC side" in "Using
MML Commands" in section 8.4.5 Activation.
On the NodeB side
To activate Ethernet OAM (IEEE 802.3ah) on the NodeB side, run the ACT ETHOAM3AH
command with the following parameters specified:

SingleRAN
l Work Mode: This parameter specifies the working mode of Ethernet OAM (IEEE
802.3ah).
l Detection Period: This parameter specifies the interval at which a Protocol Data Unit
(PDU) is transmitted for fault detection.
l PDUSIZE: This parameter specifies the length of an OAM PDU packet supported by
l Set the following parameters related to the time windows and thresholds for links
– Error Frame Event Duration
– Error Frame Event Threshold
– Error Frame Seconds Summary Event Duration
– Error Frame Seconds Summary Event Threshold

On the RNC side
The MML command examples for activating Ethernet OAM (IEEE 802.3ah) on the RNC side
are the same as those on the BSC side. For details, see "On the BSC side" in "MML
On the NodeB side

//Activating Ethernet OAM (IEEE 802.3ah)
ACT ETHOAM3AH: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, WORKMODE=ACTIVE,
PDUSIZE=128, ERRFRMEVTPRD=1, ERRFRMEVTTHD=1, ERRFRMSCDEVTPRD=60,
ERRFRMSCDEVTTHD=1;
Using the CME

The RNC and NodeB support using the CME single configuration to activate Ethernet OAM
(IEEE 802.3ah). The RNC does not support using the CME batch configuration to activate
Ethernet OAM (IEEE 802.3ah), but the NodeB does. For details, see section 8.6.5 Activation.
Using MML Commands

On the RNC side
The activation observation using MML commands on the RNC side is the same as that on the
BSC side. For details, see "On the BSC side" in Using MML Commands in section 8.4.6
Activation Observation.
On the NodeB side
Run the DSP ETHOAM3AH command to query the current status of Ethernet OAM (IEEE
802.3ah). If the value of Current State is Discover Phase, Ethernet OAM (IEEE 802.3ah)
has been activated.
None

SingleRAN
8.5.8 Deactivation
Using MML Commands

On the RNC side
RNC side is the same as that on the BSC side. For details, see "On the BSC side" in Using
MML Commands in section 8.4.8 Deactivation.
On the NodeB side
Run the DEA ETHOAM3AH command to deactivate Ethernet OAM (IEEE 802.3ah) on a
port configured with EFM OAM.

On the RNC side
The MML command examples for deactivating Ethernet OAM (IEEE 802.3ah) on the RNC
side are the same as those on the BSC side. For details, see "On the BSC side" in MML
Command Examples in section 8.4.8 Deactivation.
On the NodeB side
//Deactivating Ethernet OAM (IEEE 802.3ah)
DEA ETHOAM3AH: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0;
8.6 Deployment of Ethernet OAM (IEEE 802.3ah) for LTE
8.6.1 Requirements
Hardware
Ethernet ports.
NE IEEE 802.3ah
eNodeB LMPT/UMPT/UTRP2/UTRP9/UTRPc
IEEE 802.3ah The transmission equipment supports Ethernet OAM (IEEE 802.3ah).
License

SingleRAN
Feature ID Feature Model License NE Sales Unit

Name Control
Item
LOFD-003004 Ethernet LT1S0 Ethernet Macro Per eNodeB

OAM 0EOA OAM(FDD) eNodeB/ (FDD)
M00 LampSite
eNodeB/
BTS3202E
TDLOFD-00300 Ethernet LT1ST Ethernet LTE TDD Per eNodeB

4 OAM 0EOA OAM(TDD eNodeB (TDD)
M00 )

The data to prepare before activating Ethernet OAM (IEEE 802.3ah) on the eNodeB side is
the same as that on the NodeB side. For details, see Table 8-3.
8.6.3 Precautions
None

None
8.6.5 Activation
NOTE
To enable Ethernet OAM (IEEE802.3ah) on the eNodeB side, you should also enable it on the
Using MML Commands

eNodeB side is the same as that on the NodeB side. For details, see "On the NodeB side" in
"Using MML Commands" in section 8.5.5 Activation.

The MML command examples for activating Ethernet OAM (IEEE 802.3ah) on the eNodeB
Using the CME

For detailed operations, see CME-based Feature Configuration.

SingleRAN

The activation observation using MML commands on the eNodeB side is the same as that on
Observation.
None
8.6.8 Deactivation
Using MML Commands

On the eNodeB side
eNodeB side is the same as that on the NodeB side. For details, see "On the NodeB side" in
Using MML Commands in section 8.5.8 Deactivation.

The MML command examples for deactivating Ethernet OAM (IEEE 802.3ah) on the
eNodeB side are the same as those on the NodeB side. For details, see "On the NodeB side" in
MML Command Examples in section 8.5.8 Deactivation.
8.7 Deployment of Ethernet OAM (IEEE 802.1ag) or

Ethernet OAM (ITU-T Y.1731) for GSM
8.7.1 Requirements
Hardware
The following boards support Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.
1731) when they are configured with Ethernet ports.
NE IEEE 802.1ag ITU-T Y.1731
BSC FG2a/FG2c/FG2d/FG2e/GOUa/GOUc/GOUd/ Not supported

EXOUa/EXOUb
GBTS GTMUb/GTMUc/UTRPc UTRPc
eGBTS UMPT/GTMUb/GTMUc UMPT/GTMUc

SingleRAN
Protocol Requirement for Transmission

Equipment
Ethernet OAM (IEEE 802.1ag) The peer transmission equipment supports

Ethernet OAM (IEEE 802.1ag).
Ethernet OAM (ITU-T Y.1731) The peer transmission equipment supports

Ethernet OAM (ITU-T Y.1731).
License
No additional license is required.

Table 8-4 and Table 8-5 list the data to prepare before activating Ethernet OAM (IEEE
802.1ag) or Ethernet OAM (ITU-T Y.1731) on the BSC and GBTS sides, respectively. The
data to prepare before activating Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.
1731) on the eGBTS side is the same as that on the NodeB side. For details, see Table 8-6.
Table 8-4 Data to prepare before activating Ethernet OAM (IEEE 802.1ag) or Ethernet OAM
(ITU-T Y.1731) on the BSC side
MO Parameter Parameter ID Setting Notes Data
Name Source
CFM Subrack No. SRN(BSC6900,BSC69 -- Network

MD 10) plan
(negotiatio
n not
required)
Slot No. SN(BSC6900,BSC691 -- Network

0) plan
(negotiatio
n not
required)
MD Index MDIDX(BSC6900,BS An MD index corresponds Network

C6910) to an MD name. The value plan
of the (negotiatio
MDIDX(BSC6900,BSC6 n not
910) parameter for a CFM required)
MD must be unique on the
BSC side. The BSC
supports a maximum of 7
MDs.

SingleRAN

Name Source
MD Name MDName(BSC6900,B -- Network

SC6910) plan
(negotiatio
n not
required)
MD Level LEVEL(BSC6900,BS -- Network

C6910) plan
(negotiatio
n not
required)

MD 10) plan
(negotiatio
n not
required)
Slot No. SN(BSC6900,BSC691 -- Network

0) plan
(negotiatio
n not
required)
MD Index MDIDX(BSC6900,BS -- Network

C6910) plan
(negotiatio
n not
required)
CFM MA Index MAIDX(BSC6900,BS An MA index corresponds Network

MA C6910) to an MA name. The value plan
of the MAIDX parameter (negotiatio
for a CFM MD must be n not
unique on the BSC side. A required)
CFM MD can contain a
maximum of 500 MAs
whose indexes range from
0 to 499.
MA Name MANAME(BSC6900, -- Network

BSC6910) plan
(negotiatio
n not
required)

SingleRAN

Name Source
VLAN ID VLANID(BSC6900,BS VLAN of the MA in the Network

C6910) MD. Ethernet CFM plan
supports that an MA can (negotiatio
be created for each VLAN n not
within an MD. An MA required)
must correspond to a
VLAN ID.
CCM Send CCMINTERVAL(BSC -- Network

Prid 6900,BSC6910) plan
(negotiatio
n not
required)
VLAN VLANPRI(BSC6900,B VLAN priority. In Network

Priority SC6910) Ethernet networking, plan
VLAN priorities are used (negotiatio
to differentiate the n not
priorities of packets at the required)
data link layer. 0 indicates
the lowest priority and 7
indicates the highest
priority. The system will
send data packets with a
higher priority when links
are congested.

MEP 10) plan
(for (negotiatio
local n not
MEP required)
confi
gurati MA Index MAIDX(BSC6900,BS An MA index corresponds Network
on) C6910) to an MA name. The value plan
of the (negotiatio
MAIDX(BSC6900,BSC69 n not
10) parameter for a CFM required)
BSC side. A CFM MD
can contain a maximum of
500 MAs whose indexes
range from 0 to 499.
MEP Type MEPTYPE(BSC6900, Set this parameter based Network

BSC6910) on the network plan. The plan
MEPTYPE(BSC6900,BS (negotiatio
C6910) for the local MEP n not
is set to required)
LocalMep(LocalMep).

SingleRAN

Name Source
MEP ID MEPID(BSC6900,BS Set this parameter based Network

C6910) on the network plan. The plan
value of the (negotiatio
MEPID(BSC6900,BSC69 n not
10) parameter for the local required)
MEP must be unique
within an MA.
Port Type PORTTYPE(BSC6900 -- Network

,BSC6910) plan
(negotiatio
n not
required)
Trunk No. TRUNKN(BSC6900,B -- Network

SC6910) plan
(negotiatio
n not
required)
CFM MA Index MAIDX(BSC6900,BS Set this parameter based Network

MEP C6910) on the network plan. An plan
(for MA index corresponds to (negotiatio
remot an MA name. The value n not
e of the required)
MEP MAIDX(BSC6900,BSC69
confi 10) parameter for a CFM
gurati MD must be unique on the
on) BSC side. A CFM MD
can contain a maximum of
500 MAs whose indexes
range from 0 to 499.
MEP Type MEPTYPE(BSC6900, Set this parameter based Network

BSC6910) on the network plan. The plan
MEPTYPE(BSC6900,BS (negotiatio
C6910) for the local MEP n not
is set to required)
RemoteMep(RemoteMe
p).
MEP ID MEPID(BSC6900,BS Set this parameter based Network

C6910) on the network plan. The plan
value of the (negotiatio
MEPID(BSC6900,BSC69 n not
10) parameter for the local required)
MEP must be unique
within an MA.

SingleRAN
(ITU-T Y.1731) on the GBTS side
MO Param Parameter ID Setting Notes Data
eter Source
Name
BTSETH Ethern OAMTYPE(BSC69 Ethernet OAM Type can Network

OAM et 00,BSC6910) only be set to plan
OAM IEEE_802_1AG(IEEE (negotiation
Type 802.1ag), or not required)
ITU_T_Y1731(ITU-T Y.
1731).
Monito MONITORPOLIC This parameter is valid only Network

r Y(BSC6900,BSC69 when Ethernet OAM Type plan
Policy 10) is set to (negotiation
ITU_T_Y1731(ITU-T Y. not required)
1731). It is recommended
that the
MONITORPOLICY(BSC69
00,BSC6910) parameter be
set to the default value.
BTSETH MD MDNAME(BSC690 Set this parameter based on Network

MD Name 0,BSC6910) the network plan. The value plan
of the (negotiation
MDNAME(BSC6900,BSC6 not required)
910) parameter for a CFM
GBTS side.
This parameter can be set to
any value if OAM Type is
set to ITU-T Y.1731.
MD MDLEVEL(BSC69 A maximum of eight CFM Network

Level 00,BSC6910) MDs can be configured on a plan
NodeB. The value of the (negotiation
MDLEVEL(BSC6900,BSC6 not required)
910) parameter in the CFM
MD ranges from 0 to 7.

SingleRAN

eter Source
Name
BTSETH MD MDNAME(BSC690 Before adding a CFM MA, Network

MA Name 0,BSC6910) add a CFM MD for the CFM plan
MA under the BTSETHMA (negotiation
MO. The value of not required)
MDNAME(BSC6900,BSC6
910) in the ADD
BTSETHMA command
must be the same as that in
the ADD BTSETHMD
command.
If OAM Type is set to
1731), replace MEG ID with
MA Name. The value of the
MA Name parameter must
be unique within an MEG.
MA MANAME(BSC690 An MA is identified by an Network

Name 0,BSC6910) MD name and an MA name. plan
If OAM Type is set to (negotiation
ITU_T_Y1731(ITU-T Y. not required)
1731), replace MEG ID with
MA Name parameter must
be unique within an MEG.
VLAN VLANID(BSC6900, Do not set Network

ID BSC6910) VLANID(BSC6900,BSC691 plan
0) of a CFM MA to a VLAN (negotiation
ID for other CFM MDs. not required)
BTSETH MD MDNAME(BSC690 Before setting this parameter Network

LCMEP Name 0,BSC6910) based on the network plan, plan
configure this parameter for (negotiation
the BTSETHMD MO. not required)
MA MANAME(BSC690 Before setting this parameter Network

Name 0,BSC6910) based on the network plan, plan
configure this parameter for (negotiation
the BTSETHMA MO. not required)
MEP MEPID(BSC6900, Set this parameter based on Network

ID BSC6910) the network plan. The value plan
of the (negotiation
MEPID(BSC6900,BSC6910 not required)
) parameter for the local
MEP must be unique within
an MA.

SingleRAN

eter Source
Name
BTSETH MD MDNAME(BSC690 Configure this parameter for Network

RMMEP Name 0,BSC6910) the BTSETHMD MO. plan
(negotiation
not required)
MA MANAME(BSC690 -- Network
Name 0,BSC6910) plan
(negotiation
not required)
MEP MEPID(BSC6900, Before checking the Network

ID BSC6910) continuity between a GBTS plan
and a remote MEP, configure (negotiation
this parameter for the remote not required)
MEP on the GBTS. In
addition, the configured
remote MEP must be
consistent with that
configured on the existing
peer system in terms of MD
name, MA name, and MEP
ID. Otherwise, the remote
MEP cannot work properly.
8.7.3 Precautions
Ethernet OAM (ITU-T Y.1731) does not support packet loss measurement on an Ethernet
trunk. If packets are calculated for the Ethernet trunk, the performance monitoring data is not
accurate because the sequence of packets is not saved for the Ethernet trunk.
NOTE
To check packet loss statistics for an Ethernet trunk, you can run the DSP ETHTRK command or use
the performance counters in the Measurement of Trunk Performance (TRUNK) function set.

None
8.7.5 Activation
This section describes how to activate Ethernet OAM (IEEE802.1ag) using the MML
commands and CME GUI, and uses the scenario shown in Figure 4-2 as an example.
NOTE
l To enable Ethernet OAM (IEEE802.1ag) on the base station side, you should also enable it on the
l To enable Ethernet OAM (IEEE802.1ag) on the base station controller side, you should also enable
it on the transmission equipment.

SingleRAN
Using MML Commands

On the BSC side
Step 1 Run the ADD CFMMD command to add a CFM MD. In this step, set the following
parameters to appropriate values: MDIDX(BSC6900,BSC6910),
LEVEL(BSC6900,BSC6910), and MDNAME(BSC6900,BSC6910).
Step 2 Run the ADD CFMMA command to add an MA. In this step, set the parameters as follows:
Set MDIDX(BSC6900,BSC6910), VLANID(BSC6900,BSC6910),
MAIDX(BSC6900,BSC6910), MANAME(BSC6900,BSC6910) to appropriate values. Set
CCMINTERVAL(BSC6900,BSC6910) to a period of sending CCM packets in the MA.
Step 3 Run the ADD CFMMEP command to add a local MEP. In this step, set MEP Type to
LocalMep(LocalMep).
Step 4 Run the ADD CFMMEP command to add a remote MEP. In this step, set MEP Type to
RemoteMep(RemoteMep).
----End
The preceding steps are used for configuration. The following steps are used for continuity
check and performance management.
l Run the ACT CFMCCMTST command to activate the CC function at a specified local
MEP.
l Run the PING MAC command to start a MAC PING test on the BSC side. During the
implementation of the MAC PING test, ensure that the CC function is enabled at the
local MEP and remote MEP so that the local MEP can obtain the MAC address of the
remote MEP.
l Run the TRC MAC command to start a MAC TRACE test on the BSC side. During the
implementation of the MAC TRACE test, ensure that the CC function is enabled at the
remote MEP.
On the GBTS side
Step 1 Run the SET BTSETHOAM command with Ethernet OAM Type set to
IEEE_802_1AG(IEEE 802.1ag) or ITU_T_Y1731(ITU-T Y.1731). If this parameter is set
to ITU_T_Y1731(ITU-T Y.1731), Monitor Policy must be configured.
Step 2 Run the ADD BTSETHMD command to add a CFM MD.
Step 3 Run the ADD BTSETHMA command to add an MA.
Step 4 Run the ADD BTSETHLCMEP command to add a local MEP.
Step 5 Run the ADD BTSETHRMMEP command to add a remote MEP.
----End
l Run the ACT BTSETHCC command to activate the CC function at a specified local
MEP.
l Run the PING BTSCFM command to start a MAC PING test on the GBTS side. During
the implementation of the MAC PING test, ensure that the CC function is enabled at the

SingleRAN
remote MEP.
l Run the TRC BTSCFM command to start a MAC TRACE test on the GBTS side.
During the implementation of the MAC TRACE test, ensure that the CC function is
enabled at the local MEP and remote MEP so that the local MEP can obtain the MAC
address of the remote MEP.
If Ethernet OAM (ITU-T Y.1731) is activated:
l Run the ACT BTSETHLM command to activate the single-ended ETH-LM function at
a specified local MEP.
l Run the ACT BTSETHDM command to activate the two-way ETH-DM function at a
specified local MEP.
On the eGBTS side
The procedure for activating Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.
1731) using MML commands on the eGBTS side is the same as that on the NodeB side. For
details, see "On the NodeB side" in "Using MML Commands" in section 8.8.5 Activation.

On the BSC side
//Adding an MD on the FG2c board
ADD CFMMD: SRN=0, SN=18, MDIDX=0, LEVEL=0, MDNAME="md0";
//Adding an MA
ADD CFMMA: SRN=0, SN=18, MDIDX=0, VLANID=2, MAIDX=0, MANAME="ma0";
//Adding a local MEP
ADD CFMMEP: SRN=0, MAIDX=0, MEPTYPE=LocalMep, MEPID=1, PORTTYPE=ETHER, SN=18,
PN=0;
//Adding a remote MEP
ADD CFMMEP: SRN=0, MAIDX=0, MEPTYPE=RemoteMep, MEPID=11, SN=18;
//Activating the CC function
ACT CFMCCMTST: SRN=0, SN=18, MAIDX=0, MEPID=1;
//Starting a CFM LB test
PING MAC:
SRN=0,SN=18,MAIDX=0,SRCMEPID=1,DESTMEPID=11,Count=5,PKTSize=95,TimeOut=3;
//Starting a CFM LT test
TRC MAC: SRN=0, SN=18,MAIDX=0,SRCMEPID=1,DESTMEPID=11,TTL=60, TimeOut=5;
On the GBTS side

//Setting the OAM type
//Configuring Ethernet OAM (IEEE 802.1ag)
SET BTSETHOAM:IDTYPE=BYID,BTSID=7,OAMTYPE=IEEE_802_1AG;
//Configuring Ethernet OAM (ITU-T Y.1731)
SET BTSETHOAM:IDTYPE=BYID,BTSID=7,OAMTYPE=ITU_T_Y1731,MONITORPOLICY=SA_DA_VLANID;
//Adding an Ethernet OAM MD
ADD BTSETHMD:IDTYPE=BYID,BTSID=7,MDNAME="CHINA",MDLEVEL=7;
//Adding an Ethernet OAM MA
ADD BTSETHMA: IDTYPE=BYID, BTSID=7, MDNAME="CHINA", MANAME="SHANGHAI",
VLANSWITCH=ON, VLANID=3;
ADD BTSETHLCMEP:IDTYPE=BYID,BTSID=7,MDNAME="CHINA",MANAME="SHANGHAI",MEPID=1,PN=0;
ADD BTSETHRMMEP:IDTYPE=BYID,BTSID=7,MDNAME="CHINA",MANAME="SHANGHAI",MEPID=2;
//Activating the CC function
ACT BTSETHCC:IDTYPE=BYID,BTSID=7,MDNAME="CHINA",MANAME="SHANGHAI",MEPID=1;
PING BTSCFM: IDTYPE=BYID, BTSID=7, MDName=" CHINA ", MANAME=" SHANGHAI
",DSTTYPE=RMEP, DESTMEPID=2;

SingleRAN
//Starting CFM Loopback

CFMPING: MDNAME="CHINA", MANAME="SHANGHAI", DSTTYPE=MAC, MAC="00E2-FC00-57B7";
//Starting an LT test
TRC BTSCFM: IDTYPE=BYID, BTSID=7, MDName="CHINA", MANAME="SHANGHAI",
DSTTYPE=RMEP, DESTMEPID=2;
//Starting a single-ended ETH-LM
ACT BTSETHLM: IDTYPE=BYID, MDNAME="CHINA", MANAME="SHANGHAI", DSTTYPE=MAC,
MAC="00E2-FC00-57B7";
//Starting a two-way delay variation measurement
ACT BTSETHDM: IDTYPE=BYID, MDNAME="CHINA", MANAME="SHANGHAI", DSTTYPE=MAC,
MAC="00E2-FC00-57B7";
On the eGBTS side
The MML command examples for activating Ethernet OAM (IEEE 802.1ag) or Ethernet
OAM (ITU-T Y.1731) on the eGBTS side are the same as those on the NodeB side. For
details, see "On the NodeB side" in "MML Command Examples" in section 8.8.5 Activation.
Using the CME

The BSC, GBTS, and eGBTS support using the CME single configuration to activate
Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731). Neither the BSC nor
GBTS supports using CME batch configuration to activate Ethernet OAM (IEEE802.1ag) or
Ethernet OAM (ITU-TY.1731), but the eGBTS does. For details, see "Using the CME to
Perform Batch Configuration" in section 8.6.5 Activation.
Using MML Commands

On the BSC side
Before using the following methods, ensure that the CC function is enabled at the local and
remote ends.
Method 1: Run the DSP CFMMEP command to query the status and MAC address of the
remote MEP. If the value of MAC Address is that of the remote port, Ethernet OAM (IEEE
802.1ag) or Ethernet OAM (ITU-T Y.1731) has been activated.
Method 2: Run the PING MAC or TRC MAC command to start an LB or LT test from the
local MEP to the remote MEP. If the MAC address of the remote MEP is pinged through,
Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731) has been activated. If the
MAC address of the remote MEP cannot be pinged through, Ethernet OAM (IEEE 802.1ag)
or Ethernet OAM (ITU-T Y.1731) has not been activated.
On the GBTS side
Before using the following method, ensure that the CC function is enabled at the local and
remote ends.
Run the PING BTSCFM or TRC BTSCFM command to start an LB or LT test from the
local MEP to the remote MEP. If the MAC address of the remote MEP is pinged through,
Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731) has been activated. If the
MAC address of the remote MEP cannot be pinged through, Ethernet OAM (IEEE 802.1ag)
or Ethernet OAM (ITU-T Y.1731) has not been activated.
On the eGBTS side

SingleRAN
The activation observation using MML commands on the eGBTS side is the same as that on
Observation.
If the base station supports Ethernet OAM (IEEE 802.1ag) and you need to change the
configuration of Ethernet OAM (IEEE 802.1ag) to the configuration of Ethernet OAM (ITU-
T Y.1731), delete the configured MDs, MAs, MEPs, and RMEPs for Ethernet OAM (IEEE
802.1ag) as follows:
The following steps are used to change the configuration of Ethernet OAM (IEEE 802.1ag) to
the configuration of Ethernet OAM (ITU-T Y.1731):
On the GBTS side
Step 1 Run the RMV BTSETHRMMEP command to delete a remote MEP.
Step 2 Run the RMV BTSETHLCMEP command to delete a local MEP.
Step 3 Run the RMV BTSETHMA command to delete an MA.
Step 4 Run the RMV BTSETHMD command to delete a CFM MD.
Step 5 Run the SET BTSETHOAM command with OAM Type set to ITU-T Y.1731.
----End
On the eGBTS side
Step 1 Run the RMV CFMBNDIP command to delete a CFM binding IP address of the remote
MEP, which is used to implement the route interlock.
Step 2 Run the RMV CFMRMEP command to delete a remote MEP.
Step 3 Run the RMV CFMMEP command to delete a local MEP.
Step 4 Run the RMV CFMMA command to delete an MA.
Step 5 Run the RMV CFMMD command to delete a CFM MD.
Step 6 Run the SET ETHOAM command with OAM Type set to ITU-T Y.1731.
----End
If you need to change the configuration of Ethernet OAM (ITU-T Y.1731) to the
configuration of Ethernet OAM (IEEE 802.1ag), perform the similar operation.
8.7.8 Deactivation
This feature can be deactivated by deleting all configurations in reverse order.
Using MML Commands

On the BSC side
Step 1 Run the RMV CFMMEP command to delete a remote MEP. In this step, set MEP Type to
RemoteMep(RemoteMep).

SingleRAN
Step 2 Run the RMV CFMMEP command to delete a local MEP. In this step, set MEP Type to
LocalMep(LocalMep).
----End
On the GBTS side
Step 1 Run the RMV BTSETHRMMEP command to delete a remote MEP.
Step 2 Run the RMV BTSETHLCMEP command to delete a local MEP.
Step 3 Run the RMV BTSETHMA command to delete an MA.
Step 4 Run the RMV BTSETHMD command to delete a CFM MD.
----End

On the BSC side
//Deleting a remote MEP
RMV CFMMEP: SRN=0, SN=18, MAIDX=0, MEPID=11;
//Deleting a local MEP
RMV CFMMEP: SRN=0, SN=18, MDIDX=0, MEPID=1;
//Deleting an MA
RMV CFMMA: SRN=0, SN=18, MAIDX=0;
//Deleting an MD
RMV CFMMD: SRN=0, SN=18, MDIDX=0;
On the GBTS side

RMV BTSETHRMMEP: IDTYPE=BYID, BTSID=7, MDNAME="CHINA", MANAME="SHANGHAI", MEPID=2;
RMV BTSETHLCMEP: IDTYPE=BYID, BTSID=7, MDNAME="CHINA", MANAME="SHANGHAI", MEPID=1;
//Deleting an MA
RMV BTSETHMA: IDTYPE=BYID, BTSID=7, MDNAME="CHINA", MANAME="SHANGHAI";
//Deleting an MD
RMV BTSETHMD: IDTYPE=BYID, BTSID=7, MDNAME="CHINA";
//Setting the OAM type
SET BTSETHOAM: IDTYPE=BYID,BTSID=7,OAMTYPE="IEEE_802_1ag";
SET BTSETHOAM:
IDTYPE=BYID,BTSID=7,OAMTYPE="ITU_T_Y1731",MONITORPOLICY="SA_DA_VLANID";
On the eGBTS side

The MML command examples for deactivating Ethernet OAM (IEEE 802.1ag) or Ethernet
OAM (ITU-T Y.1731) on the eGBTS side are the same as those on the NodeB side. For
details, see "On the NodeB side" in "MML Command Examples" in section 8.8.8
Deactivation.

Ethernet OAM (ITU-T Y.1731) for UMTS

SingleRAN
8.8.1 Requirements
Hardware
RNC FG2a/FG2c/FG2d/FG2e/GOUa/GOUc/GOUd/EXOUa/ Not supported

EXOUb
NodeB WMPT/UMPT/UTRP2/UTRP9/UTRPc UMPT or UTRPc
Ethernet OAM (IEEE 802.1ag) The peer transmission equipment supports

Ethernet OAM (IEEE 802.1ag).
Ethernet OAM (ITU-T Y.1731) The peer transmission equipment supports

Ethernet OAM (ITU-T Y.1731).
License
Feature ID Protocol Feature License License NE Sales

Name Control Control Unit
Item ID Item
WRFD-050 IEEE Ethernet LQW9ET Ethernet NodeB Per

425 802.1ag OAM OAM01 OAM (per NodeB
NodeB)
ITU-T Y. Ethernet LQW9ET Ethernet NodeB Per

1731 OAM OAM01 OAM (per NodeB
NodeB)

Common Data Preparation
Table 8-6 lists the data to prepare before activating Ethernet OAM (IEEE 802.1ag) or
Ethernet OAM (ITU-T Y.1731) on the NodeB side. The data to prepare before activating this
feature on the RNC side is the same as that on the BSC side. For details, see Table 8-4.

SingleRAN
(ITU-T Y.1731) on the NodeB side
MO Parameter Parameter Setting Notes Data
Name ID Source
GTRANSPA Ethernet OAMTYPE OAM Type can only be set to Network

RA OAM Type IEEE_802_1AG(IEEE plan
802.1ag) or (negotiati
ITU_T_Y1731(ITU-T Y. on not
1731). required)
Monitor MONITOR This parameter is valid only Network

Policy POLICY when OAM Type is set to plan
ITU_T_Y1731(ITU-T Y. (negotiati
1731). It is recommended that on not
this parameter be set to the required)
default value.
CFMMD MD Name MDNAME Set this parameter based on the Network

network plan. The value of the plan
MD Name parameter for a (negotiati
CFM MD must be unique on on not
the NodeB side. required)
This parameter can be set to
any value if OAM Type is set
to ITU_T_Y1731(ITU-T Y.
1731).
MD Level LEVEL A maximum of eight CFM Network

MDs can be configured on a plan
NodeB. (negotiati
The value of this parameter on not
ranges from 0 to 7. required)
If OAM Type is set to
1731), the value of LEVEL is
used to indicate the MEG level
of ITU_T_Y.1731.
CFMMA MD Name MDNAME Before adding a CFM MA, Network

configure this parameter for the plan
MA under the CFMMD MO. (negotiati
The value of MD Name in on not
CFM MA must be the same as required)
that in the CRM MD.
This parameter is invalid only
when OAM Type is set to
1731).

SingleRAN

Name ID Source
MA Name MANAME An MA is identified by an MD Network

name and an MA name. plan
If OAM Type is set to (negotiati
ITU_T_Y1731(ITU-T Y. on not
1731), replace MEG ID with required)
MA Name parameter must be
unique within an MEG.
Binding BNDVLAN Set this parameter based on the Network

VLAN network plan. This parameter plan
specifies whether an MA is (negotiati
bound with a VLAN. MAs on not
must be bound with VLANs required)
for continuity check on
Ethernet ports or link
aggregation groups. The
binding is not required for
continuity check on member
ports in a link aggregation
group.
VLAN ID VLANID Set this parameter based on the Network

network plan. If BNDVLAN is plan
set to YES(Yes) for a CFM (negotiati
MA, do not set VLANID to a on not
VLAN ID for other CFM MAs. required)
VLAN VLANPRI This parameter is valid only Network

Priority when BNDVLAN is set to YES plan
for a CFM MA. (negotiati
on not
required)
CFMMEP MD Name MDNAME Before setting this parameter Network

based on the network plan, plan
configure this parameter for the (negotiati
CFMMD MO. on not
required)
MA Name MANAME Before setting this parameter Network

CFMMA MO. on not
required)
MEP ID MEPID Set this parameter based on the Network

network plan. The value of the plan
MEP ID parameter for the (negotiati
local MEP must be unique on not
within an MA. required)

SingleRAN

Name ID Source
CFMRMEP MD Name MDNAME Before setting this parameter Network

CFMMD MO. on not
required)
MA Name MANAME Before setting this parameter Network

CFMMA MO. on not
required)
RMEP ID RMEPID Before checking the continuity Network

between a NodeB and a remote plan
MEP, configure this parameter (negotiati
for the remote MEP on the on not
NodeB side. In addition, the required)
configured remote MEP must
be consistent with that
configured on the existing peer
system in terms of MD name,
MA name, and MEP ID.
Otherwise, the remote MEP
cannot work properly.
MAC MAC The MAC address must be a Network

Address unicast address. The MAC plan
address of the remote MEP is (negotiati
obtained from the CCM on not
message. If the MAC address required)
obtained from the CCM
message is different from the
configured MAC, the obtained
MAC address prevails. Set this
parameter on the network plan.
If multiple remote MEPs are
configured in a CFM MA, use
different MAC addresses for
these remote MEPs. Otherwise,
the CFM LB test may become
abnormal.
Scenario-Specific Data Preparation

If route interlock is required based on the CFM CC result, bind the remote MEP to an IP
address. The route interlock function is supported only by the NodeB or eNodeB after the CC
function in the CFMMEP MO is activated in the summary data file. Table 8-7 lists the
parameters related to the route interlock function.

SingleRAN
Table 8-7 Parameters related to the route interlock function

NE M Parame Parameter ID Data Source Setting
O ter Notes
Name
NodeB CF MD MDNAME Before setting this Network

MB Name parameter based on the plan
NDI network plan, configure (negotiati
P this parameter for the on not
CFMMD MO. required)
MA MANAME Before setting this Network

Name parameter based on the plan
network plan, configure (negotiati
this parameter for the on not
CFMMA MO. required)
RMEP RMEPID Before setting this Network

ID parameter based on the plan
network plan, configure (negotiati
this parameter for the on not
CFMRMEP MO. required)
IP BNDIP Set this parameter based on Network

Address the network plan. This plan
parameter specifies the IP (negotiati
address of the Ethernet port on not
or the Ethernet link required)
aggregation group
corresponding to the
remote MEP.
l Do not perform route
interlock to the active
and standby IP routes
by using CFM and
bidirectional forwarding
detection (BFD).
l Do not bind two
CFMRMEPs in an MA
to the same IP address.
The bound IP address
must be different from
that of all configured or
working ports
(including physical
ports and loopback
ports) on the local
equipment.
RNC Non None None None None

e

SingleRAN
8.8.3 Precautions
NOTE

None
8.8.5 Activation
Using MML Commands
On the RNC side
1731) using MML commands on the RNC side is the same as that on the BSC side. For
details, see "On the BSC side" in "Using MML Commands" in section 8.7.5 Activation.
On the NodeB side
Step 1 Run the SET ETHOAM command with OAMTYPE set to IEEE_802_1AG(IEEE 802.1ag)
or ITU_T_Y1731(ITU-T Y.1731). If this parameter is set to ITU_T_Y1731(ITU-T Y.1731),
Monitor Policy must be configured.
Step 2 Run the ADD CFMMD command to add a CFM MD.
Step 3 Run the ADD CFMMA command to add a CFM MA.
Step 4 Run the ADD CFMMEP command to add a local MEP.
Step 5 Run the ADD CFMRMEP command to add a remote MEP.
Step 6 Run the ADD CFMBNDIP command to add an RMEP binding IP address. The binding
address can also be used for routes.
----End
l Run the ACT CFMCC command to activate the CC function at a specified local MEP.
l Run the CFMPING command to start the CFM MAC PING test on the NodeB side.
During the implementation of the MAC PING test, ensure that the CC function is
l Run the CFMTRACE command to start the CFM MAC TRACE test on the NodeB
side. During the implementation of the MAC TRACE test, ensure that the CC function is
If Ethernet OAM (ITU-T Y.1731) is activated:

SingleRAN
l Run the ACT ETHLM command to activate the single-ended ETH-LM function at a
specified local MEP.
l Run the ACT ETHDM command to activate the measurement of bidirectional delay
variation on the local MEP.

On the RNC side
OAM (ITU-T Y.1731) on the RNC side are the same as those on the BSC side. For details, see
"On the BSC side" in "MML Command Examples" in section 8.7.5 Activation.
On the NodeB side
SET ETHOAM:OAMTYPE=IEEE_802_1AG;
SET ETHOAM:OAMTYPE=ITU_T_Y1731,MONITORPOLICY=SA_DA_VLANID;
//Adding a CFM MD
ADD CFMMD:MDNAME="CHINA",LEVEL=7;
//Adding a CFM MA
ADD CFMMA:MDNAME="CHINA",MANAME="SHANGHAI",SN=6,BNDVLAN=YES,VLANID=3;
ADD
CFMMEP:MDNAME="CHINA",MANAME="SHANGHAI",MEPID=1000,SN=6,SBT=BASE_BOARD,PT=ETH,PN=0
;
ADD CFMRMEP: MDNAME="CHINA", MANAME="SHANGHAI", RMEPID=2000, MAC="0023-8956-7895";
//Activating the CFM CC function
ACT CFMCC:MDNAME="CHINA",MANAME="SHANGHAI",MEPID=1000;
CFMPING: MDNAME="CHINA", MANAME="SHANGHAI", DSTTYPE=MAC, MAC="00E2-FC00-57B7";
//Starting a single-ended ETH-LM
ACT ETHLM: MDNAME="CHINA", MANAME="SHANGHAI", MEPID=1000, DSTTYPE=MAC, MAC="00E2-
FC00-57B7";
//Starting a two-way delay variation measurement
ACT ETHDM: MDNAME="CHINA", MANAME="SHANGHAI", MEPID=1000, DSTTYPE=MAC, MAC="00E2-
FC00-57B7";
Using the CME

The RNC and NodeB support using the CME single configuration to activate Ethernet OAM
(IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731). The RNC does not support using the CME
batch configuration to activate Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.
1731), but the NodeB does. For details, see "Using the CME" in 8.6.5 Activation.

On the RNC side
Before using the following methods, ensure that the CC function is enabled at the local and
remote ends.
l Run the DSP CFMMEP command to check the RMEP status and the MAC address.
If MEP Type is Remote Mep and MAC Address is the MAC address of the remote
port, Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731) has been
activated.
l Run the PING MAC or TRC MAC command to start an LB or LT test from the local
MEP to the remote MEP.

SingleRAN
– If the MAC address of the remote MEP is pinged through, Ethernet OAM (IEEE
802.1ag) or Ethernet OAM (ITU-T Y.1731) has been activated.
– If the MAC address of the remote MEP cannot be pinged through, Ethernet OAM
(IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731) has not been activated.
On the NodeB side

l Run the DSP CFMRMEP command to check the RMEP status and the MAC address.
If the Actual MAC Address is the MAC address of the remote port and Status is
Normal, Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731) has been
activated.
l Run the CFMPING or CFMTRACE command and set Destination Type to
RMEP(RMEP) start an LB or LT test from the local MEP to the remote MEP.
– If the remote MEP is pinged through, Ethernet OAM (IEEE 802.1ag) or Ethernet
OAM (ITU-T Y.1731) has been activated.
– If the remote MEP cannot be pinged through, Ethernet OAM (IEEE 802.1ag) or
Ethernet OAM (ITU-T Y.1731) has been activated.
NOTE
Before using the preceding methods, ensure that the CC function is enabled at the local and remote
ends.
l In scenarios where the remote MEP and MAC address are known, run the CFMPING or
CFMTRACE. In this command, set Destination Type to MAC(Remote MAC
Address) and enter MAC Address to check the connectivity.
NOTE
The CC function is not required for this observation method.
If the base station supports Ethernet OAM (IEEE 802.1ag)/Ethernet OAM (ITU-T Y.1731)
and you need to need to change the configuration of Ethernet OAM (IEEE 802.1ag) to the
configuration of Ethernet OAM (ITU-T Y.1731) or vice versa, delete the configured MDs,
MAs, MEPs, and RMEPs for Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.
1731) as follows:
The following steps are used to change the configuration of Ethernet OAM (IEEE 802.1ag) to
the configuration of Ethernet OAM (ITU-T Y.1731):
On the NodeB side

SingleRAN
Step 6 To change the configuration of Ethernet OAM (IEEE 802.1ag) to the configuration of
Ethernet OAM (ITU-T Y.1731) on the NodeB side, do as follows: run the SET ETHOAM
command with OAMTYPE set to ITU_T_Y1731(ITU-T Y.1731).
----End
8.8.8 Deactivation
Deactivation is to delete all relevant configuration.
Using MML Commands

On the RNC side
The procedure for deactivating Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.
1731) using MML command on the RNC side is the same as that on the BSC side. For details,
see "On the BSC side" in "Using MML Commands" in 8.7.8 Deactivation.
On the NodeB side
----End

On the RNC side
1731) using MML command on the RNC side is the same as that on the BSC side. For details,
see "On the BSC side" in "Using MML Commands" in 8.7.8 Deactivation.
On the NodeB side

RMV CFMRMEP: MDNAME="CHINA", MANAME="SHANGHAI", RMEPID=2000;
RMV CFMMEP: MDNAME="CHINA", MANAME="SHANGHAI", MEPID=1000;
//Deleting a CFM MA
RMV CFMMA: MDNAME="CHINA", MANAME="SHANGHAI";
//Deleting a CFM MD
RMV CFMMD: MDNAME="CHINA";

Ethernet OAM (ITU-T Y.1731) for LTE

SingleRAN
8.9.1 Requirements
Hardware
eNodeB LMPT/UMPT/UTRP2/UTRP9/UTRPc LMPT/UMPT/ UTRPc
Ethernet OAM (IEEE 802.1ag) The peer transmission equipment supports Ethernet
OAM (IEEE 802.1ag).
Ethernet OAM (ITU-T Y.1731) The peer transmission equipment supports Ethernet
OAM (ITU-T Y.1731).
License
Feature ID Feature Model License NE Sales Unit

Name Control
Item
LOFD-003004 Ethernet LT1S00E Ethernet eNodeB Per eNodeB

OAM OAM00 OAM(FDD) (FDD) (FDD)
TDLOFD-003 Ethernet LT1ST0E Ethernet LTE TDD Per eNodeB

004 OAM OAM00 OAM(TDD) eNodeB (TDD)

The data to prepare before activating Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-
T Y.1731) on the eNodeB side is the same as that on the NodeB side. For details, see Table
8-6.
8.9.3 Precautions
NOTE

SingleRAN

None
8.9.5 Activation
Using MML Commands

1731) using MML commands on the eNodeB side is the same as that on the NodeB side. For
details, see "On the NodeB side" in "Using MML Commands" in section 8.8.5 Activation.

OAM (ITU-T Y.1731) on the eNodeB side are the same as those on the NodeB side. For
details, see "On the NodeB side" in "MML Command Example" in section 8.8.5 Activation.
Using the CME

For detailed operations, see CME-based Feature Configuration.
Using MML Commands

The activation observation procedure on the eNodeB side is the same as that on the UMTS
NodeB side. For details, see "On the NodeB side" in section 8.8.6 Activation Observation.
The reconfiguration procedure on the eNodeB side is the same as that on the NodeB side. For
details, see "On the NodeB side" in section 8.8.7 Reconfiguration.
8.9.8 Deactivation
Using MML Commands

1731) using MML commands on the eNodeB side is the same as that on the NodeB side. For
details, see "On the NodeB side" in "Using MML Commands" in section 8.8.8 Deactivation.

The MML command examples for deactivating Ethernet OAM (IEEE 802.1ag) or Ethernet
OAM (ITU-T Y.1731) on the eNodeB side are the same as those on the NodeB side. For
details, see "On the NodeB side" in "MML Command Examples" in section 8.8.8
Deactivation.

SingleRAN
8.10 Performance Monitoring

For details about the CCM, see section "Activation Observation" for each feature. The
performance of Ethernet OAM (ITU-T Y.1731) involves single-ended ETH-LM, two-way
ETH-DM, and delay variation measurement in real time. You can perform the following
operations for real-time monitoring:
l ITU-T Y.1731 single-ended ETH-LM
a. Run the DSP ETHLM command to check the status of the Ethernet packet loss.
b. Obtain the values of the following counters from the real-time monitoring interface:
Total number of frames transmitted in the uplink
Total number of lost frames transmitted in the uplink
Total number of frames transmitted in the downlink
Total number of lost frames transmitted in the downlink
c. Observe the values of the following counters:
VS.ETHLM.Forward.DropMeans: Forward average Ethernet packet loss rate
VS.ETHLM.Forward.Peak.DropRates: Forward peak Ethernet packet loss rate
VS.ETHLM.Forward.MinDropRates: Forward minimum Ethernet packet loss
rate
VS.ETHLM.Backward.DropMeans: Backward average Ethernet packet loss rate
VS.ETHLM.Backward.Peak.DropRates: Backward peak Ethernet packet loss
rate
VS.ETHLM.Backward.MinDropRates: Backward minimum Ethernet packet loss
rate
l ITU-T Y.1731 two-way ETH-DM and delay variation measurement
a. Run the DSP ETHDM command to check the status of the two-way ETH-DM and
delay variation.
b. Obtain the values of the following counters from the real-time monitoring interface:
Average delay
Average delay variation
c. Observe the values of the following counters:
VS.ETHDM.MaxRttDelay: Maximum Ethernet RTT delay
VS.ETHDM.MinRttDelay: Minimum Ethernet RTT delay
VS.ETHDM.Rtt.Means: Average Ethernet RTT delay
VS.ETHDM.RttJitterStandardDeviation: Standard Ethernet RTT delay variation
deviation
VS.ETHDM.MinRttJitter: Minimum Ethernet RTT delay variation
VS.ETHDM.RttJitter.Means: Average Ethernet RTT delay variation
VS.ETHDM.MaxRttJitter: Maximum Ethernet RTT delay variation
l Ethernet OAM (ITU-T Y.1731) does not support packet loss measurement on an
Ethernet trunk. For packet loss statistics on an Ethernet trunk, observe the values of the
following counters:
VS.TRUNK.TxPackets: Number of packets transmitted in TRUNK

SingleRAN
VS.TRUNK.RxPackets: Number of packets received in TRUNK

VS.TRUNK.RxErrPackets: Number of error packets received in TRUNK
8.11 Parameter Optimization

None
8.12 Possible Issues

On the BSC or RNC side
If link faults occur or the remote end does not support the Ethernet OAM feature, OAM
discovery fails. In this case, ALM-21371 ETHOAM 3AH Detection Failure is reported. You
can troubleshoot the problem following the steps provided in the alarm help.
After the remote loopback function provided by Ethernet OAM (IEEE 802.3ah) is enabled by
running the BSC/RNC MML command STR EFMLOOPTST, ALM-21374 ETHOAM 3AH
Remote Loopback is reported due to service congestion if the remote loopback succeeds. This
alarm is cleared when the remote loopback test ends.
On the NodeB, eNodeB, or eGBTS side
If Ethernet OAM (IEEE 802.3ah) is abnormal, check whether the alarms listed in Table 8-8
are reported. If yes, clear these alarms following the steps provided in handling suggestions.
Table 8-8 Alarms related to Ethernet OAM (IEEE 802.3ah)

Alarm ID Alarm Name Alarm Severity
25882 ETHOAM 3AH Discovery Failure Minor
25884 ETHOAM 3AH Remote Fault Minor
25894 ETHOAM 3AH Remote Loopback Major
If ALM-25880 Ethernet Link Fault or ALM-25895 Ethernet Trunk Group Fault is reported
after the CFM CC function is enabled on the Ethernet port or Ethernet trunk group of the base
station and peer NE, clear the alarm with actions recommended for each alarm cause listed in
Table 8-9. The Ethernet trunk group and ALM-25895 Ethernet Trunk Group Fault are
supported by macro base stations only.

SingleRAN
Table 8-9 Alarms related to Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.
1731)
Alarm Alarm Name Alar
ID m
Seve
rity
25880 Ethernet Link Fault Major

This alarm is reported with either of the following cause values (the
last three are newly added):
l Ethernet Link Fault
l CCM LOS Fault
l AIS Fault
l RDI Fault
If alarms with the cause value "Ethernet Link Fault" are reported,
alarms with other cause values are masked. If no alarms with the
cause value "Ethernet Link Fault" are reported, the alarms with
other cause values are reported.
25895 Ethernet Trunk Group Fault (supported by macro base stations only) Major
This alarm is reported with either of the following newly added cause
values:
l CCM LOS Fault
l AIS Fault
l RDI Fault
When an Ethernet port in the Ethernet trunk group is faulty, this alarm
is reported without a cause value and alarms with cause values are
masked. If no alarms without a cause value are reported, the alarms
with cause values are reported.
On the GBTS side

For details about the troubleshooting procedure, see section 8.7.6 Activation Observation.

SingleRAN
Ethernet OAM Feature Parameter Description 9 Parameters
9 Parameters
Table 9-1 Parameters

Parame NE MML Feature Feature Description
ter ID Comma ID Name
nd
MDNA BTS390 ADD WRFD- Ethernet Meaning: Indicates the name of the CFM MD.
ME 0, CFMM 050425 OAM GUI Value Range: 1~43 characters
BTS390 D
0 LOFD-0 Ethernet Unit: None
DSP 0300402 OAM(I
WCDM CFMM Actual Value Range: 1~43 characters
A, / EEE
D TDLOF 802.1ag) Default Value: None
BTS390
0 LTE RMV D-00300
CFMM 402 Ethernet
D OAM
GBFD-1
LST 18630
CFMM
D

SingleRAN

nd
LEVEL BTS390 ADD WRFD- Ethernet Meaning: Indicates the level of the CFM MD.
0, CFMM 050425 OAM GUI Value Range: 0~7
BTS390 D
DSP 0300402 OAM(I
WCDM CFMM Actual Value Range: 0~7
A, / EEE
D TDLOF 802.1ag) Default Value: 0
BTS390
0 LTE DSP D-00300
CFMM 402 Ethernet
A OAM
GBFD-1
DSP 18630
CFMM
EP
DSP
CFMR
MEP
LST
CFMM
D
SRN BSC690 ADD None None Meaning: The subrack number for running this
0 CFMM command
D GUI Value Range: 0~11
RMV Unit: None
CFMM
D Actual Value Range: 0~11
Default Value: None
SRN BSC691 ADD None None Meaning: The subrack number for running this
0 CFMM command
RMV Unit: None
CFMM
Default Value: None
SN BSC690 ADD None None Meaning: Indicates the slot number for running this
0 CFMM command.
D GUI Value Range: 0~5;8~27
RMV Unit: None
CFMM
D Actual Value Range: 0~5, 8~27
Default Value: None

SingleRAN

nd
SN BSC691 ADD None None Meaning: Indicates the slot number for running this
0 CFMM command
RMV Unit: None
CFMM
Default Value: None
MDIDX BSC690 ADD GBFD-1 Ethernet Meaning: Identifies a maintenance domain

0 CFMM 18630 OAM GUI Value Range: 0~7
D
Unit: None
RMV
CFMM Actual Value Range: 0~7
D Default Value: None

D
Unit: None
RMV
D Default Value: None
MDNa BSC690 ADD GBFD-1 Ethernet Meaning: name of the MD

me 0 CFMM 18630 OAM GUI Value Range: 1~20 characters
D
Unit: None
Actual Value Range: 1~20 characters
Default Value: None
MDNa BSC691 ADD GBFD-1 Ethernet Meaning: name of the MD

me 0 CFMM 18630 OAM GUI Value Range: 1~20 characters
D
Unit: None
Default Value: None
Level BSC690 ADD GBFD-1 Ethernet Meaning: Class of the maintenance domain
D
Unit: None
Actual Value Range: 0~7
Default Value: 0

SingleRAN

nd
Level BSC691 ADD GBFD-1 Ethernet Meaning: Class of the maintenance domain
D
Unit: None
Default Value: 0
MAIDX BSC690 ADD GBFD-1 Ethernet Meaning:

0 CFMM 18630 OAM Identifies a maintenance group. Maintenance group:
A maintenance alliance (MA), which is a component of
RMV the maintenance domain (MD). One MD can be
CFMM divided into one or more maintenance groups.
A The range of the MA index is 0~99 for one pair of
active and standby FG2a or GOUa boards, or 0~499
for one pair of active and standby FG2d, FG2c, FG2e,
GOUd, GOUc or GOUe boards. The range of the
independent board is the same as the range of active
and standby boards.
GUI Value Range: 0~499
Unit: None
Default Value: None

A maintenance alliance (MA), which is a component of
A The range of the MA index is 0~499 for one pair of
active and standby FG2d, FG2c, FG2e, GOUd, GOUc
or GOUe boards, or 0~2999 for EXOUa, EXOUb or
EXOUc board. The range of the independent board is
the same as the range of active and standby boards.
Unit: None
Default Value: None
MANA BSC690 ADD GBFD-1 Ethernet Meaning: Name of the MA

ME 0 CFMM 18630 OAM GUI Value Range: 1~20 characters
A
Unit: None
Default Value: None

SingleRAN

nd
MANA BSC691 ADD GBFD-1 Ethernet Meaning: Name of the MA

ME 0 CFMM 18630 OAM GUI Value Range: 1~20 characters
A
Unit: None
Default Value: None
VLANI BSC690 ADD GBFD-1 Ethernet Meaning: Specifies the identifier of a VLAN.
D 0 CFMM 18630 OAM Connectivity Fault Management (CFM) supports the
A creation of a Maintenance Association (MA) on each
VLAN for each Maintenance Domain (MD) Level.
The MA must be in one-to-one mapping with the
VLAN ID.
Unit: None
Default Value: None
VLANI BSC691 ADD GBFD-1 Ethernet Meaning: Specifies the identifier of a VLAN.
D 0 CFMM 18630 OAM Connectivity Fault Management (CFM) supports the
A creation of a Maintenance Association (MA) on each
VLAN for each Maintenance Domain (MD) Level.
The MA must be in one-to-one mapping with the
VLAN ID.
Unit: None
Default Value: None
CCMIN BSC690 ADD GBFD-1 Ethernet Meaning: Transmission period of the CCM packet in
TERVA 0 CFMM 18630 OAM the MA
L A GUI Value Range: 10, 100, 1000
Unit: ms
Actual Value Range: 10, 100, 1000
Default Value: 1000
CCMIN BSC691 ADD GBFD-1 Ethernet Meaning: Transmission period of the CCM packet in
TERVA 0 CFMM 18630 OAM the MA
L A GUI Value Range: 10, 100, 1000
Unit: ms
Actual Value Range: 10, 100, 1000
Default Value: 1000

SingleRAN

nd
VLANP BSC690 ADD None None Meaning: Priority of the VLAN. The VLAN priority
RI 0 CFMM is used to prioritize packets at the data link layer in an
A Ethernet. 0 indicates the lowest priority. 7 indicates
the highest priority. The high-priority packets are
preferentially transmitted during congestion of links.
Unit: None
Default Value: 6
VLANP BSC691 ADD None None Meaning: Priority of the VLAN. The VLAN priority
RI 0 CFMM is used to prioritize packets at the data link layer in an
A Ethernet. 0 indicates the lowest priority. 7 indicates
the highest priority. The high-priority packets are
preferentially transmitted during congestion of links.
Unit: None
Default Value: 6
SRN BSC690 ADD MRFD- Configu Meaning: Number of the subrack

0 CFMM 210301 ration GUI Value Range: 0~11
EP Manage
ment Unit: None
RMV
EP Default Value: None
SRN BSC691 ADD MRFD- Configu Meaning: Number of the subrack

0 CFMM 210301 ration GUI Value Range: 0~11
EP Manage
ment Unit: None
RMV
EP Default Value: None

SingleRAN

nd

EP maintenance alliance (MA), which is a component of
EP The range of the MA index is 0~99 for one pair of
active and standby FG2a or GOUa boards, or 0~499
for one pair of active and standby FG2d, FG2c, FG2e,
GOUd, GOUc or GOUe boards. The range of the
independent board is the same as the range of active
and standby boards.
Unit: None
Default Value: None

EP maintenance alliance (MA), which is a component of
EP The range of the MA index is 0~499 for one pair of
active and standby FG2d, FG2c, FG2e, GOUd, GOUc
or GOUe boards, or 0~2999 for EXOUa, EXOUb or
EXOUc board. The range of the independent board is
the same as the range of active and standby boards.
Unit: None
Default Value: None
MEPT BSC690 ADD GBFD-1 Ethernet Meaning: The type of the maintenance point added to
YPE 0 CFMM 18630 OAM the maintenance group. LocalMep indicates a local
EP maintenance point and RemoteMep indicates a remote
maintenance point.
GUI Value Range: LocalMep(LocalMep),
RemoteMep(RemoteMep)
Unit: None
Actual Value Range:
LocalMep,
RemoteMep
Default Value: None

SingleRAN

nd
MEPT BSC691 ADD GBFD-1 Ethernet Meaning: The type of the maintenance point added to
YPE 0 CFMM 18630 OAM the maintenance group. LocalMep indicates a local
EP maintenance point and RemoteMep indicates a remote
maintenance point.
GUI Value Range: LocalMep(LocalMep),
RemoteMep(RemoteMep)
Unit: None
Actual Value Range:
LocalMep,
RemoteMep
Default Value: None
MEPID BSC690 ADD GBFD-1 Ethernet Meaning:

0 CFMM 18630 OAM Identifies a maintenance point in the maintenance
EP alliance.
RMV A maintenance point is an edge node of the MA.
CFMM
EP GUI Value Range: 1~1000
Unit: None
Default Value: None
MEPID BSC691 ADD GBFD-1 Ethernet Meaning:

0 CFMM 18630 OAM Identifies a maintenance point in the maintenance
EP alliance
RMV A maintenance point is an edge node of the MA.
CFMM
EP GUI Value Range: 1~3000
Unit: None
Default Value: None
PORTT BSC690 ADD GBFD-1 Ethernet Meaning: Indicates the type of the physical port .
YPE 0 CFMM 18630 OAM ETHER indicates the ethernet port and TRUNK
EP indicates the aggregation group.
GUI Value Range: ETHER, TRUNK
Unit: None
Actual Value Range: ETHER, TRUNK
Default Value: None

SingleRAN

nd
PORTT BSC691 ADD GBFD-1 Ethernet Meaning: Indicates the type of the physical port .
YPE 0 CFMM 18630 OAM ETHER indicates the ethernet port and TRUNK
EP indicates the aggregation group.
GUI Value Range: ETHER, TRUNK
Unit: None
Actual Value Range: ETHER, TRUNK
Default Value: None
TRUN BSC690 ADD GBFD-1 Ethernet Meaning: TRUNK group number.

KN 0 CFMM 18630 OAM GUI Value Range: 0~11
EP
Unit: None
Default Value: None
TRUN BSC691 ADD GBFD-1 Ethernet Meaning: TRUNK group number.

KN 0 CFMM 18630 OAM GUI Value Range: 0~11
EP
Unit: None
Default Value: None
OAMT BSC690 SET GBFD-1 Ethernet Meaning: Indicates the type of BTS Ethernet OAM.
YPE 0 BTSET 18630 OAM GUI Value Range: IEEE_802_1AG(IEEE 802.1ag),
HOAM ITU_T_Y1731(ITU-T Y.1731)
Unit: None
Actual Value Range: IEEE_802_1AG, ITU_T_Y173
Default Value: IEEE_802_1AG(IEEE 802.1ag)
OAMT BSC691 SET GBFD-1 Ethernet Meaning: Indicates the type of BTS Ethernet OAM.
YPE 0 BTSET 18630 OAM GUI Value Range: IEEE_802_1AG(IEEE 802.1ag),
HOAM ITU_T_Y1731(ITU-T Y.1731)
Unit: None
Actual Value Range: IEEE_802_1AG, ITU_T_Y173
Default Value: IEEE_802_1AG(IEEE 802.1ag)

SingleRAN

nd
MONIT BSC690 SET GBFD-1 Ethernet Meaning: This parameter indicates monitoring policy,
ORPOL 0 BTSET 18630 OAM and is valid only if "OAMTYPE" is set to
ICY HOAM ITU_T_Y1731.
GUI Value Range: PORTID_VLANID(Based on
PortID and VLANID),
PORTID_VLANID_VLANPRI(Based on
PortID,VLANID and VLAN PRI),
SA_DA_VLANID(Based on SA,DA and VLANID),
SA_DA_VLANID_VLANPRI(Based on
SA,DA,VLANID and VLAN PRI), SA_DA(Based on
SA and DA)
Unit: None
Actual Value Range: PORTID_VLANID,
PORTID_VLANID_VLANPRI, SA_DA_VLANID,
SA_DA_VLANID_VLANPRI, SA_DA
Default Value: PORTID_VLANID_VLANPRI(Based
on PortID,VLANID and VLAN PRI)
MONIT BSC691 SET GBFD-1 Ethernet Meaning: This parameter indicates monitoring policy,
ORPOL 0 BTSET 18630 OAM and is valid only if "OAMTYPE" is set to
ICY HOAM ITU_T_Y1731.
PortID and VLANID),
SA and DA)
Unit: None
MDNA BSC690 ADD GBFD-1 Ethernet Meaning: Name of the maintenance domain.
ME 0 BTSET 18630 OAM GUI Value Range: 1~20 characters
HMD
Unit: None
RMV
BTSET Actual Value Range: 1~20 characters
HMD Default Value: None

SingleRAN

nd
HMD
Unit: None
RMV
HMD Default Value: None
MDLE BSC690 ADD GBFD-1 Ethernet Meaning: Level of the maintenance domain.The
VEL 0 BTSET 18630 OAM priority of the maintenance domain ranks from 0 to 7
HMD from low to high.
Unit: None
Default Value: 0
MDLE BSC691 ADD GBFD-1 Ethernet Meaning: Level of the maintenance domain.The
VEL 0 BTSET 18630 OAM priority of the maintenance domain ranks from 0 to 7
HMD from low to high.
Unit: None
Default Value: 0
HMA
Unit: None
RMV
HMA Default Value: None
HMA
Unit: None
RMV
MANA BSC690 ADD GBFD-1 Ethernet Meaning: Name of the maintenance association.
HMA
Unit: None
RMV

SingleRAN

nd
HMA
Unit: None
RMV
VLANI BSC690 ADD GBFD-1 Ethernet Meaning: VLAN ID of the service type.
D 0 BTSET 18630 OAM GUI Value Range: 1~4094
HMA
Unit: None
Default Value: 1
VLANI BSC691 ADD GBFD-1 Ethernet Meaning: VLAN ID of the service type.
D 0 BTSET 18630 OAM GUI Value Range: 1~4094
HMA
Unit: None
Default Value: 1
HLCM
EP Unit: None
RMV Actual Value Range: 1~20 characters

BTSET Default Value: None
HLCM
EP
HLCM
EP Unit: None

HLCM
EP
HLCM
EP Unit: None

HLCM
EP

SingleRAN

nd
HLCM
EP Unit: None

HLCM
EP
MEPID BSC690 ADD GBFD-1 Ethernet Meaning: Identifies a maintenance end point (MEP) of
0 BTSET 18630 OAM a maintenance association.
HLCM GUI Value Range: 1~8191
EP
Unit: None
RMV
BTSET Actual Value Range: 1~8191
HLCM Default Value: None
EP
HLCM GUI Value Range: 1~8191
EP
Unit: None
RMV
HLCM Default Value: None
EP
HRMM
EP Unit: None

HRMM
EP
HRMM
EP Unit: None

HRMM
EP

SingleRAN

nd
HRMM
EP Unit: None

HRMM
EP
HRMM
EP Unit: None

HRMM
EP
HRMM GUI Value Range: 1~8191
EP
Unit: None
RMV
HRMM Default Value: None
EP
HRMM GUI Value Range: 1~8191
EP
Unit: None
RMV
HRMM Default Value: None
EP

A
Unit: None
Default Value: None

SingleRAN

nd

A
Unit: None
Default Value: None
OAMT BTS390 SET LOFD-0 Ethernet Meaning: Indicates the type of Ethernet OAM. The
YPE 0, ETHO 0300402 OAM current Ethernet OAM type includes IEEE 802.1ag or
BTS390 AM / (IEEE ITU-T Y.1731 ETHOAM.
0 LST TDLOF 802.1ag) GUI Value Range: IEEE_802_1AG(IEEE 802.1ag),
WCDM ETHO D-00300 Ethernet ITU_T_Y1731(ITU-T Y.1731)
A, AM 402 OAM
BTS390 Unit: None
LOFD-0 (Y.1731)
0 LTE 0300403 Actual Value Range: IEEE_802_1AG, ITU_T_Y1731
/ Ethernet Default Value: IEEE_802_1AG(IEEE 802.1ag)
TDLOF OAM
D-00300
403
GBFD-1
18630

SingleRAN

nd
MONIT BTS390 SET LOFD-0 Ethernet Meaning: Indicates the ITU-T Y.1731 monitoring
ORPOL 0, ETHO 0300403 OAM policy. The monitoring policy includes the following
ICY BTS390 AM / (Y.1731) values: PORTID_VLANID (based on PortID and
0 LST TDLOF VLANID), PORTID_VLANID_VLANPRI (based on
WCDM D-00300 Ethernet PortID, VLANID, and VLAN PRI),
ETHO OAM
A, AM 403 SA_DA_VLANID (based on PortID, source MAC
BTS390 address, destination MAC address, and VLANID),
0 LTE GBFD-1 SA_DA_VLANID_VLANPRI (based on PortID,
18630 source MAC address, destination MAC address,
VLANID, and VLAN PRI), and SA_DA (based on
PortID, source MAC address, and destination MAC
address).
PortID and VLANID),
SA and DA)
Unit: None
MDNA BTS390 ADD WRFD- Ethernet Meaning: Indicates the name of the MD to which the
ME 0, CFMM 050425 OAM MA belongs.
BTS390 A GUI Value Range: 1~43 characters
0 LOFD-0 Ethernet
DSP 0300402 OAM(I Unit: None
WCDM CFMM
A, / EEE Actual Value Range: 1~43 characters
A TDLOF 802.1ag)
BTS390 Default Value: None
0 LTE MOD D-00300
CFMM 402 Ethernet
A OAM
GBFD-1
RMV 18630
CFMM
A
LST
CFMM
A

SingleRAN

nd
MANA BTS390 ADD WRFD- Ethernet Meaning: Indicates the name of the MA.
ME 0, CFMM 050425 OAM GUI Value Range: 1~43 characters
BTS390 A
DSP 0300402 OAM(I
WCDM CFMM Actual Value Range: 1~43 characters
A, / EEE
A TDLOF 802.1ag) Default Value: None
BTS390
0 LTE MOD D-00300
CFMM 402 Ethernet
A OAM
GBFD-1
RMV 18630
CFMM
A
LST
CFMM
A
BNDVL BTS390 ADD WRFD- Ethernet Meaning: Indicates whether the MA is associated with
AN 0, CFMM 050425 OAM the VLAN.
BTS390 A GUI Value Range: NO(No), YES(Yes)
0 LOFD-0 Ethernet
WCDM CFMM
A, / EEE Actual Value Range: NO, YES
A TDLOF 802.1ag)
BTS390 Default Value: YES(Yes)
0 LTE LST D-00300
CFMM 402 Ethernet
A OAM
GBFD-1
18630
VLANI BTS390 ADD WRFD- Ethernet Meaning: Indicates the ID of the VLAN with which
D 0, CFMM 050425 OAM the MA is associated.
BTS390 A GUI Value Range: 1~4094
0 LOFD-0 Ethernet
WCDM CFMM
A, / EEE Actual Value Range: 1~4094
A TDLOF 802.1ag)
BTS390 Default Value: 1
0 LTE LST D-00300
CFMM 402 Ethernet
A OAM
GBFD-1
18630

SingleRAN

nd
VLANP BTS390 ADD WRFD- Ethernet Meaning: Indicates the priority of the VLAN with
RI 0, CFMM 050425 OAM which the MA is associated.
BTS390 A GUI Value Range: 0~7
0 LOFD-0 Ethernet
MOD 0300402 OAM(I Unit: None
WCDM CFMM
A, / EEE Actual Value Range: 0~7
A TDLOF 802.1ag)
BTS390 Default Value: 0
0 LTE DSP D-00300
CFMM 402 Ethernet
A OAM
GBFD-1
LST 18630
CFMM
A
MDNA BTS390 ACT WRFD- Ethernet Meaning: Indicates the name of the MD to which the
ME 0, CFMC 050425 OAM MEP belongs.
BTS390 C GUI Value Range: 1~43 characters
0 LOFD-0 Ethernet
ADD 0300402 OAM(I Unit: None
WCDM CFMM
EP TDLOF 802.1ag)
0 LTE DEA D-00300
CFMC 402 Ethernet
C OAM
GBFD-1
DSP 18630
CFMM
EP
RMV
CFMM
EP
LST
CFMM
EP

SingleRAN

nd
MANA BTS390 ACT WRFD- Ethernet Meaning: Indicates the name of the MA to which the
ME 0, CFMC 050425 OAM MEP belongs.
BTS390 C GUI Value Range: 1~43 characters
0 LOFD-0 Ethernet
ADD 0300402 OAM(I Unit: None
WCDM CFMM
EP TDLOF 802.1ag)
0 LTE DEA D-00300
CFMC 402 Ethernet
C OAM
GBFD-1
DSP 18630
CFMM
EP
RMV
CFMM
EP
LST
CFMM
EP
MEPID BTS390 ACT WRFD- Ethernet Meaning: Indicates the MEP ID.
0, CFMC 050425 OAM GUI Value Range: 1~8191
BTS390 C
ADD 0300402 OAM(I
WCDM CFMM Actual Value Range: 1~8191
A, / EEE
EP TDLOF 802.1ag) Default Value: None
BTS390
0 LTE DEA D-00300
CFMC 402 Ethernet
C OAM
GBFD-1
DSP 18630
CFMM
EP
RMV
CFMM
EP
LST
CFMM
EP

SingleRAN

nd
ME 0, CFMR 050425 OAM RMEP belongs.
BTS390 MEP GUI Value Range: 1~43 characters
0 LOFD-0 Ethernet
WCDM CFMR
MEP TDLOF 802.1ag)
0 LTE RMV D-00300
CFMR 402 Ethernet
MEP OAM
GBFD-1
LST 18630
CFMR
MEP
MANA BTS390 ADD WRFD- Ethernet Meaning: Indicates the name of the MA to which the
ME 0, CFMR 050425 OAM RMEP belongs.
BTS390 MEP GUI Value Range: 1~43 characters
0 LOFD-0 Ethernet
WCDM CFMR
MEP TDLOF 802.1ag)
0 LTE RMV D-00300
CFMR 402 Ethernet
MEP OAM
GBFD-1
LST 18630
CFMR
MEP
RMEPI BTS390 ADD WRFD- Ethernet Meaning: Indicates the RMEP ID.
D 0, CFMR 050425 OAM GUI Value Range: 1~8191
BTS390 MEP
DSP 0300402 OAM(I
WCDM CFMR Actual Value Range: 1~8191
A, / EEE
MEP TDLOF 802.1ag) Default Value: None
BTS390
0 LTE RMV D-00300
CFMR 402 Ethernet
MEP OAM
GBFD-1
LST 18630
CFMR
MEP

SingleRAN

nd
MAC BTS390 ADD WRFD- Ethernet Meaning: Indicates the MAC address of the RMEP. It
0, CFMR 050425 OAM must be a valid unicast address in the format of
BTS390 MEP XXXX-XXXX-XXXX. The MAC address of the
0 LOFD-0 Ethernet RMEP can be obtained from the MAC address field
DSP 0300402 OAM(I
WCDM CFMR carried in the CCM message. If the MAC address
A, / EEE configured by the user is different from that carried in
MEP TDLOF 802.1ag)
BTS390 the CCM message, the MAC address carried in the
0 LTE LST D-00300 MAC message prevails.
CFMR 402 Ethernet
MEP OAM GUI Value Range: 14 characters
GBFD-1 Unit: None
18630
Actual Value Range: 14 characters
Default Value: 0000-0000-0000
ME 0, CFMB 050425 OAM RMEP belongs.
BTS390 NDIP GUI Value Range: 1~43 characters
0 LOFD-0 Ethernet
RMV 0300402 OAM(I Unit: None
WCDM CFMB
NDIP TDLOF 802.1ag)
0 LTE LST D-00300
CFMB 402 Ethernet
NDIP OAM
GBFD-1
18630
MANA BTS390 ADD WRFD- Ethernet Meaning: Indicates the name of the MA to which the
ME 0, CFMB 050425 OAM RMEP belongs.
BTS390 NDIP GUI Value Range: 1~43 characters
0 LOFD-0 Ethernet
RMV 0300402 OAM(I Unit: None
WCDM CFMB
NDIP TDLOF 802.1ag)
0 LTE LST D-00300
CFMB 402 Ethernet
NDIP OAM
GBFD-1
18630

SingleRAN

nd
RMEPI BTS390 ADD WRFD- Ethernet Meaning: Indicates the RMEP ID.
D 0, CFMB 050425 OAM GUI Value Range: 1~8191
BTS390 NDIP
RMV 0300402 OAM(I
WCDM CFMB Actual Value Range: 1~8191
A, / EEE
NDIP TDLOF 802.1ag) Default Value: None
BTS390
0 LTE LST D-00300
CFMB 402 Ethernet
NDIP OAM
GBFD-1
18630
BNDIP BTS390 ADD WRFD- Ethernet Meaning: Indicates the IP address of the Ethernet port
0, CFMB 050425 OAM or Ethernet trunk corresponding to an RMEP. The
BTS390 NDIP binding IP address must be different from the existing
0 LOFD-0 Ethernet local IP address or the IP address of any effective port
RMV 0300402 OAM(I
WCDM CFMB (including the physical port and loopback port). The
A, / EEE binding IP address must be different from the local IP
NDIP TDLOF 802.1ag)
BTS390 address dynamically negotiated on the PPP or MLPPP
0 LTE LST D-00300 link. During the binding of an IP address, an error
CFMB 402 Ethernet
OAM messaged indicating IP address conflicts may be
NDIP displayed. In this case, list the existing IP address in
GBFD-1
18630 the system that conflicts with the IP address to be
bound by running the related MML commands. Then,
manually resolve the IP address conflicts. To list the
device IP address, run the LST DEVIP or DSP DEVIP
command. To list the local IP address of the remote
maintenance channel, run the LST OMCH or DSP
OMCH command. To list the local IP address of the
PPP link, run the LST PPPLNK or DSP PPPLNK
command. To list the local IP address of the MLPPP
group, run the LST MPGRP or DSP MPGRP
command. To list the IP address of the local
maintenance channel, run the LST LOCALIP or DSP
LOCALIP command.
GUI Value Range: Valid IP address
Unit: None
Actual Value Range: Valid IP address
Default Value: None

SingleRAN
Ethernet OAM Feature Parameter Description 10 Counters
10 Counters
Table 10-1 Counters

Counter ID Counter Counter NE Feature ID Feature Name
Name Description
1542456106 VS.ETHDM.M Maximum RTT eGBTS Multi-mode: Ethernet OAM

axRttDelay delay on the None Ethernet OAM
Ethernet GSM: None Ethernet OAM
UMTS:
WRFD-050425
LTE:
LOFD-003004
TDLOFD-0030
04
1542456107 VS.ETHDM.M Minimum RTT eGBTS Multi-mode: Ethernet OAM

inRttDelay delay on the None Ethernet OAM
UMTS:
WRFD-050425
LTE:
LOFD-003004
TDLOFD-0030
04
1542456108 VS.ETHDM.Rt Average RTT eGBTS Multi-mode: Ethernet OAM

t.Means delay on the None Ethernet OAM
UMTS:
WRFD-050425
LTE:
LOFD-003004
TDLOFD-0030
04

SingleRAN

Name Description
1542456109 VS.ETHDM.Rt Standard eGBTS Multi-mode: Ethernet OAM

tJitterStandar deviation of the None Ethernet OAM
dDeviation RTT jitter on GSM: None
the Ethernet Ethernet OAM
UMTS:
WRFD-050425
LTE:
LOFD-003004
TDLOFD-0030
04
1542456110 VS.ETHDM.M Maximum RTT eGBTS Multi-mode: Ethernet OAM

axRttJitter jitter on the None Ethernet OAM
UMTS:
WRFD-050425
LTE:
LOFD-003004
TDLOFD-0030
04
1542456111 VS.ETHDM.M Minimum RTT eGBTS Multi-mode: Ethernet OAM

inRttJitter jitter on the None Ethernet OAM
UMTS:
WRFD-050425
LTE:
LOFD-003004
TDLOFD-0030
04
1542456112 VS.ETHDM.Rt Average RTT eGBTS Multi-mode: Ethernet OAM

tJitter.Means jitter on the None Ethernet OAM
UMTS:
WRFD-050425
LTE:
LOFD-003004
TDLOFD-0030
04

SingleRAN

Name Description
1542456116 VS.ETHLM.Fo Average eGBTS Multi-mode: Ethernet OAM

rward.DropMe forward packet None Ethernet OAM
ans loss on the GSM: None
Ethernet Ethernet OAM
UMTS:
WRFD-050425
LTE:
LOFD-003004
TDLOFD-0030
04
1542456117 VS.ETHLM.Fo Peak forward eGBTS Multi-mode: Ethernet OAM

rward.Peak.Dr packet loss on None Ethernet OAM
opRates the Ethernet GSM: None Ethernet OAM
UMTS:
WRFD-050425
LTE:
LOFD-003004
TDLOFD-0030
04
1542456118 VS.ETHLM.Fo Minimum eGBTS Multi-mode: Ethernet OAM

rward.MinDro forward packet None Ethernet OAM
pRates loss on the GSM: None
Ethernet Ethernet OAM
UMTS:
WRFD-050425
LTE:
LOFD-003004
TDLOFD-0030
04
1542456119 VS.ETHLM.B Average eGBTS Multi-mode: Ethernet OAM

ackward.Drop backward None Ethernet OAM
Means packet loss on GSM: None
UMTS:
WRFD-050425
LTE:
LOFD-003004
TDLOFD-0030
04

SingleRAN

Name Description
1542456120 VS.ETHLM.B Peak backward eGBTS Multi-mode: Ethernet OAM

ackward.Peak. packet loss on None Ethernet OAM
DropRates the Ethernet GSM: None Ethernet OAM
UMTS:
WRFD-050425
LTE:
LOFD-003004
TDLOFD-0030
04
1542456121 VS.ETHLM.B Minimum eGBTS Multi-mode: Ethernet OAM

ackward.MinD backward None Ethernet OAM
ropRates packet loss on GSM: None
UMTS:
WRFD-050425
LTE:
LOFD-003004
TDLOFD-0030
04
1542456126 VS.TRUNK.Tx Number of eGBTS Multi-mode: Link

Packets packets MRFD-210103 Aggregation
transmitted in GSM: None
TRUNK Ethernet Link
UMTS: None Aggregation
LTE: (IEEE 802.3ad)
LOFD-003008 Ethernet Link
TDLOFD-0030 Aggregation
08 (IEEE 802.3ad)
1542456127 VS.TRUNK.Rx Number of eGBTS Multi-mode: Link

Packets packets MRFD-210103 Aggregation
received in GSM: None
TRUNK Ethernet Link
LTE: (IEEE 802.3ad)
08 (IEEE 802.3ad)

SingleRAN

Name Description
1542456128 VS.TRUNK.Rx Number of error eGBTS Multi-mode: Link

ErrPackets packets MRFD-210103 Aggregation
received in GSM: None
TRUNK Ethernet Link
LTE: (IEEE 802.3ad)
08 (IEEE 802.3ad)

SingleRAN
Ethernet OAM Feature Parameter Description 11 Glossary
11 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

SingleRAN
Ethernet OAM Feature Parameter Description 12 Reference Documents
12 Reference Documents
None


2-Antenna Receive Diversity (GBSS16.0 - 01)

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

2-Antenna Receive Diversity (GBSS16.0 - 01)

Enviado por

Direitos autorais:

Formatos disponíveis

SingleRAN

Ethernet OAM Feature Parameter

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2016-09-30) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

3 Ethernet OAM (IEEE 802.3ah)..................................................................................................... 6

4 Ethernet OAM (IEEE 802.1ag)................................................................................................... 12

5 Ethernet OAM (ITU-T Y.1731).................................................................................................. 16

Issue 01 (2016-09-30) Huawei Proprietary and Confidential ii

7.2 WRFD-050425 Ethernet OAM.................................................................................................................................... 25

Issue 01 (2016-09-30) Huawei Proprietary and Confidential iii

8.7.6 Activation Observation..............................................................................................................................................50

Issue 01 (2016-09-30) Huawei Proprietary and Confidential iv

1 About This Document

l GBFD-118630 Ethernet OAM

Unless otherwise specified, the following naming conventions are applied:

Table 1-1 Ethernet OAM supported by NEs of each mode

GSM base GBTS/eGBTS Supported Supported Supported

UMTS base NodeB Supported Supported Supported

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 1

Base NE Ethernet OAM Ethernet OAM Ethernet OAM

RNC Supported Supported Not supported

LTE base eNodeB Supported Supported Supported

Multimode Multimode Supported Supported Supported

1.2 Intended Audience

l Need to understand the features described herein

1.3 Change History

SRAN12.1 Draft A (2016-12-30)

Change Change Description Parameter Change

Feature Added the descriptions of the FG2e board of the None

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 2

Change Change Description Parameter Change

Editorial None None

1.4 Differences Between Base Station Types

GBFD-118630 Ethernet OAM Yes No No

WRFD-050425 Ethernet OAM Yes Yes Yes

LOFD-003004 Ethernet OAM Yes Yes Yes

TDLOFD-003004 Ethernet OAM Yes No No

Function Implementation in Macro, Micro, and LampSite Base Stations

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 3

l Helps improve operators' capabilities of managing and maintaining the Ethernet.

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 4

Figure 2-1 Position of Ethernet OAM protocols in the OSI model

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 5

3 Ethernet OAM (IEEE 802.3ah)

Figure 3-1 Ethernet OAM (IEEE 802.3ah)

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 6

Table 3-1 OAM client capabilities in different modes

Initiating automatic discovery Yes No

Responding to automatic discovery Yes Yes

Sending Information OAM PDUs Yes Yes

Sending Event Notification OAM PDUs Yes Yes

Sending Variable Request OAM PDUs Yes No

Sending Variable Response OAM PDUs Yes Yes

Sending Loopback Control OAM PDUs Yes No

Responding to Loopback Control OAM Yes Yes

Sending Organization Specific OAM Yes Yes

3.3 Application Scenarios

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 7

3.4 Technical Description

Figure 3-3 Automatic discovery procedure