ethernet oam(sran8.0_03).pdf

7/21/2019 Ethernet OAM(SRAN8.0_03).pdf

http://slidepdf.com/reader/full/ethernet-oamsran8003pdf 1/115

SingleRAN

Ethernet OAM Feature Parameter

Description

Issue 03

Date 2014-03-31

HUAWEI TECHNOLOGIES CO., LTD.



Copyright © Huawei Technologies Co., Ltd. 2014. 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: [email protected]

Issue 03 (2014-03-31) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com/



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

2.1 Introduction....................................................................................................................................................................5

2.2 Benefits...........................................................................................................................................................................5

2.3 Architecture....................................................................................................................................................................5

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

3.1 Introduction....................................................................................................................................................................7

3.2 Principles........................................................................................................................................................................7

3.3 Application Scenarios.....................................................................................................................................................8

3.4 Technical Description.....................................................................................................................................................9

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

4.1 Introduction..................................................................................................................................................................13

4.2 Principles......................................................................................................................................................................13

4.3 Application Scenarios...................................................................................................................................................15

4.4 Technical Description...................................................................................................................................................15

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

5.1 Introduction..................................................................................................................................................................17

5.2 Principles......................................................................................................................................................................17

5.3 Application Scenarios...................................................................................................................................................17

5.4 Technical Description...................................................................................................................................................18

6 Related Features...........................................................................................................................22

6.1 Ethernet OAM (IEEE 802.3ah)....................................................................................................................................22

6.2 Ethernet OAM (IEEE 802.1ag)....................................................................................................................................22

6.3 Ethernet OAM (ITU-T Y.1731)...................................................................................................................................23

7 Network Impact...........................................................................................................................25

8 Engineering Guidelines.............................................................................................................26

SingleRAN

Ethernet OAM Feature Parameter Description Contents



ii



8.1 When to Use Ethernet OAM........................................................................................................................................26

8.2 Required Information...................................................................................................................................................27

8.3 Planning........................................................................................................................................................................28

8.3.1 RF Planning...............................................................................................................................................................28

8.3.2 Network Planning......................................................................................................................................................28

8.3.3 Hardwar e Planning....................................................................................................................................................28

8.4 Deployment of Ethernet OAM (IEEE 802.3ah) for GSM............................................................................................28

8.4.1 Requirements.............................................................................................................................................................28

8.4.2 Data Pre paration........................................................................................................................................................29

8.4.3 Precautions.................................................................................................................................................................31

8.4.4 Hardwar e Adjustment................................................................................................................................................31

8.4.5 Activation..................................................................................................................................................................31

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

8.6 Deployment of Ethernet OAM (IEEE 802.3ah) for LTE.............................................................................................40

8.6.1 Requirements.............................................................................................................................................................41


8.6.3 Precautions.................................................................................................................................................................41


8.6.5 Activation..................................................................................................................................................................41



8.6.8 Deactivation...............................................................................................................................................................42

8.7 Deployment of Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731) for GSM....................................42

8.7.1 Requirements.............................................................................................................................................................43


8.7.3 Precautions.................................................................................................................................................................49


8.7.5 Activation..................................................................................................................................................................50



SingleRAN




iii



8.7.8 Deactivation...............................................................................................................................................................55

8.8 Deployment of Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731) for UMTS.................................57

8.8.1 Requirements.............................................................................................................................................................57

8.8.2 Data Preparation........................................................................................................................................................58

8.8.3 Precautions.................................................................................................................................................................64

8.8.4 Hardware Adjustment................................................................................................................................................64

8.8.5 Activation..................................................................................................................................................................64



8.8.8 Deactivation...............................................................................................................................................................70

8.9 Deployment of Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731) for LTE.....................................71

8.9.1 Requirements.............................................................................................................................................................71

8.9.2 Data Preparation........................................................................................................................................................72

8.9.3 Precautions.................................................................................................................................................................72

8.9.4 Hardware Adjustment................................................................................................................................................72

8.9.5 Activation..................................................................................................................................................................72



8.9.8 Deactivation...............................................................................................................................................................73

8.10 Performance Monitoring.............................................................................................................................................73

8.11 Parameter Optimization..............................................................................................................................................73

8.12 Troubleshooting..........................................................................................................................................................73

9 Parameters.....................................................................................................................................76

10 Counters....................................................................................................................................108

11 Glossary.....................................................................................................................................109

12 Reference Documents.............................................................................................................110

SingleRAN




iv



1 About This Document

1.1 Scope

This document describes the 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

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 StationType

NE Ethernet OAM(IEEE 802.3ah)

EthernetOAM (IEEE802.1ag)

EthernetOAM (ITU-T Y.1731)

Macro base station

(GSM)

GBTS/eGBTS Supported Supported Supported

BSC Supported Supported Not supported

Macro base station

(UMTS)

NodeB Supported Supported Supported

RNC Supported Supported Not supported

Macro base station

(LTE)

eNodeB Supported Supported supported

Macro base station Multimode

base station

Supported Supported Supported

SingleRAN

Ethernet OAM Feature Parameter Description 1 About This Document



1



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

SRAN8.0 03 (2014-03-31)

This issue includes the following changes.

Change Type Change Description ParameterChange

Feature change None None

Editorial change Added the descriptions about the feature and function

differences between different site types. For details, see

section 1.4 Differences Between Base Station Types.

None

SRAN8.0 02 (2013-07-30)



Feature change None None

Editorial change Deleted the descriptions of Ethernet OAM (IEEE

802.3ah and IEEE 802.1ag) supported by micro base

stations.

None

SRAN8.0 01 (2013-04-28)

This issue does not include any changes.

SingleRAN




2



SRAN8.0 Draft B (2013-04-10)



Feature change Added the descriptions of Ethernet OAM (IEEE

802.3ah and IEEE 802.1ag) supported by micro

base stations.

None

Editorial change None None

SRAN8.0 Draft A (2012-12-30)

This document is created for SRAN8.0.

This document normalizes the descriptions of IEEE 802.3ah and IEEE 802.1ag in the following

documents:

l IP Transport Architecture Feature Parameter Description for GBSS14.0

l IP Transport Architecture Feature Parameter Description for RAN14.0

l S1X2OM Channel Management Feature Parameter Description for eRAN3.0

Change Type Change Description Parameter Change

Feature change Added the descriptions of Ethernet

OAM (ITU-T Y.1731).

None

Editorial change None None

1.4 Differences Between Base Station Types

Feature Support by Macro, Micro, and LampSite Base Stations

Feature ID Feature Name Supportedby MacroBaseStations

Supportedby MicroBaseStations

Supportedby LampSiteBase Stations

GBFD-118630 Ethernet OAM Yes No No

WRFD-050425 Ethernet OAM Yes Yes Yes

LOFD-003004 Ethernet OAM Yes Yes Yes

SingleRAN




3



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 Yes.1731).

Working in either UMTS only or LTE FDD only mode, micro base stations also do not support

GSM, multimode, co-MPT, or separate-MPT scenarios. As integrated entities, micro base

stations do not involve such concepts as boards, cabinets, subracks, slots, or RRUs.

SingleRAN




4



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 ITU-T Y.1731.

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



5



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



6



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 dir ectly 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 remote end.

l In passive mode, the local end waits for negotiation packets from the remote end.

SingleRAN

Ethernet OAM Feature Parameter Description 3 Ethernet OAM (IEEE 802.3ah)



7



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




9



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


eGBTS/NodeB/eNodeB Error Frame Event

Duration

ERRFRMEVTPRD

Error Frame Event

Threshold

ERRFRMEVTTHD

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




10




eGBTS/NodeB/

eNodeB

Error Frame Seconds

Summary Event Duration

ERRFRMSCDEVTPRD

Error Frame Seconds

Summary Event Threshold

ERRFRMSCDEVTTHD

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


Remote Loopback

In a remote loopback, the local OAM client sends packets to the remote OAM client, and the

remote OAM clients 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

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




11



l The port works in active mode.

l The port and the peer port work properly.

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




12



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 if necessary, 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.

SingleRAN

Ethernet OAM Feature Parameter Description 4 Ethernet OAM (IEEE 802.1ag)



13



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.

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.

SingleRAN




14



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.

4.3 Application Scenarios

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)

l

Loopback (LB)l Linktrace (LT)

l 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 CCM packets 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 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.

SingleRAN




15



The LB is similar to the Ping operation and therefore is also called MAC PING.

l 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

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 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 Time to Live (TTL) parameters which

specify 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




16



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). In GSM and UMTS modes,

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). The only difference is as follows:

Ethernet OAM (ITU-T Y.1731) incorporates the following changes:

l Combines MDs and MAs 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).

5.3 Application Scenarios

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

Ethernet OAM Feature Parameter Description 5 Ethernet OAM (ITU-T Y.1731)



17



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


Ethernet OAM (ITU-T Y.1731) inherits the CFM function from 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.

When single-ended ETH-LM and two-way ETH-DM of Ethernet OAM (ITU-T Y.1731) are

supported, the base station supports only one of the following monitoring policies, not their

combinations:

l PORTID_VLANID (measurement based on PortID and VLAN ID)

l PORTID_VLANID_VLANPRI (measurement based on PortID, VLAN ID, and VLAN

PRI)

l SA_DA_VLANID (measurement based on PortID, SA, DA, and VLAN ID)

l SA_DA_VLANID_VLANPRI (measurement based on PortID, SA, DA, VLAN ID, andVLAN PRI)

l SA_DA (measurement based on PortID, SA, and DA)

PortID, VLANID, VLAN PRI, SA, and DA indicate the port ID, VLAN ID, VLAN priority,

source MAC address, and destination MAC address, respectively.

NOTE

The monitoring policy for the Performance Management function must be supported by the base station

as well as the peer transmission equipment.

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.

SingleRAN




18



Figure 5-2 Single-ended ETH-LM

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 use 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])

SingleRAN




19



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)

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[t p]

SingleRAN




20



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




21



6 Related Features

6.1 Ethernet OAM (IEEE 802.3ah)

Prerequisite Features

GSM:

GBFD-118601 Abis over IP

UMTS:

WRFD-050402 IP Transmission Introduction on Iub Interface

LTE:

None

Mutually Exclusive Features

None

Impacted Features

MRFD-210103 Link Aggregation.

Ethernet aggregation ports do not support this feature, but Ethernet aggregation member ports

support this feature.

6.2 Ethernet OAM (IEEE 802.1ag)


GSM:


UMTS:

SingleRAN

Ethernet OAM Feature Parameter Description 6 Related Features



22




LTE:

None


Ethernet OAM (IEEE 802.1ag) is mutually exclusive with Ethernet OAM (ITU-T Y.1731). This

implies that Ethernet OAM (IEEE 802.1ag) and Ethernet OAM (ITU-T Y.1731) cannot be

enabled simultaneously on a base station.

Before replacing Ethernet OAM (IEEE 802.1ag) with Ethernet OAM (ITU-T Y.1731), delete

all configurations for Ethernet OAM (IEEE 802.1ag) and then configure the data for Ethernet

OAM (ITU-T Y.1731).

Impacted Features None

6.3 Ethernet OAM (ITU-T Y.1731)


GSM:


UMTS:


LTE:

None


Ethernet OAM (ITU-T Y.1731) is mutually exclusive with Ethernet OAM (IEEE 802.1ag). This

implies that Ethernet OAM (ITU-T Y.1731) and Ethernet OAM (IEEE 802.1ag) cannot be

enabled simultaneously on a base station.

Before replacing Ethernet OAM (ITU-T Y.1731) with Ethernet OAM (IEEE 802.1ag), delete

all configurations for Ethernet OAM (ITU-T Y.1731) and then configure the data for Ethernet

OAM (IEEE 802.1ag).

Impacted Features

MRFD-210103 Link Aggregation.

When MRFD-210103 Link Aggregation is enabled:

l Ethernet aggregation ports support this feature, but Ethernet aggregation member ports do

not.

SingleRAN




23



l If this feature is enabled for Ethernet aggregation ports, its single-ended ETH-LM function

does not take effect.

SingleRAN




24



7 Network Impact

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.

SingleRAN

Ethernet OAM Feature Parameter Description 7 Network Impact



25



8 Engineering Guidelines

8.1 When to Use Ethernet OAM

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 borne by a 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 thatdirectly 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

Ethernet OAM Feature Parameter Description 8 Engineering Guidelines



26



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

NOTE

IEEE 802.1ag is

incompatible with its

draft version or EEE802.1ag (2007).

Therefore, both ends

must use the same

protocol version.

From GBSS9.0/RAN9.0 to

GBSS13.0/RAN13.0, the base

station supports only IEEE 802.1ag

(Draft 7). From GBSS14.0/

RAN14.0/eRAN3.0/SRAN7.0, the base station supports only the

standard version.

The base station controller

supports both the Draft 7 and

standard version.

ITU-T Y.1731 The base station supports ITU-T Y.

1731 (2008).

The base station controller

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




27



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, GOUa, GOUc, or GOUd

GBTS GTMUb, UTRP2, UTRP9, or UTRPc

eGBTS UMPT

Transmission Equipment

Protocol Requirement for Transmission Equipment

IEEE 802.3ah The transmission equipment supports Ethernet

OAM (IEEE 802.3ah).

SingleRAN




28



License

No additional license is required.

8.4.2 Data PreparationTable 8-1 and Table 8-2 and Table 8-5 list the data to prepare before activating Ethernet OAM

(IEEE 802.3ah) on the BSC, GBTS, and eGBTS (or NodeB) sides, respectively. The parameters

on the eGBTS side are the same as those on the NodeB side.

Table 8-1 Data to prepare before activating Ethernet OAM (IEEE 802.3ah) on the BSC side

MO Parameter Name ParameterID

Setting Notes

Data Source

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

PDU Pkt Len[Byte] PDUSize -- Network plan

(negotiation not

required)

Err Frame Event

Prid[s]

ERFAMEvent

Prid

-- Network plan

(negotiation not

required)

Err Frame Event

Para

ERFAMEvent

Para

-- Network plan

(negotiation not

required)

Err Frame Cyc Event

Prid

ERFAMPRD

EventPrid

-- Network plan

(negotiation not

required)

Err Frame Cyc Event

Para

ERFAMPRD

EventPara

-- Network plan

(negotiation not

required)

Err Frame Sec Event

Prid[s]

ERFAMSCD

EventPrid

-- Network plan

(negotiation not

required)

SingleRAN




29



MO Parameter Name ParameterID

Setting Notes

Data Source

Err Frame Sec Event

Para[s]

ERFAMSCD

EventPara

-- Network plan


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

Name

Parameter ID Setting

Notes

Data Source

BTSETHOAMA

H

PDU Send

Period

PDUPrid -- Network plan

(negotiation not

required)

PDU Packet Len PDUSize -- Network plan

(negotiation not

required)

Err Frame Event

Prid

ERFAMEventP

rid

-- Network plan

(negotiation not

required)

Err Frame Event

Para

ERFAMEventP

ara

-- Network plan

(negotiation not

required)

Err Frame Cyc

Event Prid

ERFAMPRDE

ventPrid

-- Network plan

(negotiation not

required)

Err Frame Cyc

Event Para

ERFAMPRDE

ventPara

-- Network plan

(negotiation not

required)

Err Frame Sec

Event Prid

EERFAMSCD

EventPrid

-- Network plan

(negotiation not

required)

Err Frame Sec

Event Para

ERFAMSCDE

ventPara

-- Network plan

(negotiation not

required)

NOTE


SingleRAN




30



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 and describes how to activate

Ethernet OAM (IEEE802.3ah) using the Man Machine Language (MML) and CME GUI.

NOTE

l Enable Ethernet OAM (IEEE 802.3ah) simultaneously on the BSC side and the transmission

equipment.

l Enable Ethernet OAM (IEEE 802.3ah) simultaneously on the GBTS side and the transmission

equipment.

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. PDU Send Prid[ms]: This parameter specifies the fault detection period based on the IEEE

802.3ah protocol.

2. PDU Pkt Len[Byte]: 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

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 PDU Send Period: This parameter specifies the fault detection period based on the IEEE

802.3ah protocol.

l PDU Packet Len: This parameter specifies the length of an OAM PDU packet supported

by Ethernet OAM (IEEE 802.3ah).

l Set the following parameters related to the time windows and thresholds for links defined

in IEEE 802.3ah:

SingleRAN




31



– Err Frame Event Prid

– Err Frame Event Para

– Err Frame Cyc Event Prid

–

Err Frame Cyc Event Para– Err Frame Sec Event Prid

– 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 to Perform Single Configuration

The BSC, GBTS, and eGBTS support using CME single configuration to activate Ethernet OAM

(IEEE 802.3ah).

On the CME, set parameters listed in Table 8-3 and Table 8-4 for a BSC and GBTS, respectively.

For related parameters on the eGBTS side, see Table 8-6 For detailed instructions, see CME

Single Configuration Operation Guide.

Table 8-3 Parameters related to Ethernet OAM (IEEE 802.3ah) on the BSC side

MO NE Parameter Name Parameter ID

EFMAH BSC/RNC Subrack No. SRN

Slot No. SN

Port No. PN

PDU Send Prid[ms] PDUPrid

PDU Pkt Len[Byte] PDUSize

Err Frame Event Prid[s] ERFAMEventPrid

SingleRAN




32





Err Frame Cyc Event Prid ERFAMPRDEventPrid


Err Frame Sec Event Prid EERFAMSCDEventPrid

Err Frame Sec Event Para

[s]

ERFAMSCDEventPara

Table 8-4 Parameters related to Ethernet OAM (IEEE 802.3ah) on the GBTS side

MO NE Parameter Name Parameter IDBTSETHOAMAH GBTS PDU Send Period PDUPrid

PDU Packet Len PDUSize

Err Frame Event Prid ERFAMEventPrid


Err Frame Cyc Event Prid ERFAMPRDEventPrid


Err Frame Sec Event Prid EERFAMSCDEventPrid

Err Frame Sec Event Para ERFAMSCDEventPara

Using the CME to Perform Batch Configuration

Neither the BSC nor GBTS supports using CME batch configuration to activate Ethernet OAM

(IEEE 802.3ah), but the eGBTS does. For details, see section Using the CME to Perform Batch

Configuration.

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.

SingleRAN




33



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.

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.

MML Command ExamplesOn the BSC side

//Deactivating the EFM OAM function on the FG2a board

DEA EFMAH: SRN=0,SN=18,PORTNO=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

side are the same as those on the NodeB side. For details, see "On the NodeB side" in MMLCommand Examples in section 8.5.8 Deactivation.

8.5 Deployment of Ethernet OAM (IEEE 802.3ah) for UMTS

8.5.1 Requirements

Hardware

The following boards support Ethernet OAM (IEEE 802.3ah) when they are configured with

Ethernet ports.

SingleRAN




34



NE IEEE 802.3ah

RNC FG2a, FG2c, FG2d, GOUa, GOUc, or GOUd

NodeB WMPT, UMPT, UTRP2, UTRP9, or UTRPc


Protocol Requirement for TransmissionEquipment

IEEE 802.3ah The transmission equipment supports

Ethernet OAM (IEEE 802.3ah).

License

Feature ID FeatureName

License ControlItem ID

Supported NEType

Sales Unit

WRFD-050425 Ethernet

OAM

Ethernet OAM (per

NodeB)

NodeB per NodeB

8.5.2 Data Preparation

Data to prepare before activating Ethernet OAM (IEEE 802.3ah) on the RNC side is the same

as that on the BSC side. For details, see Table 8-1. Table 8-5 lists the data to prepare before

activating this feature on the NodeB side.

Table 8-5 Data to prepare before activating Ethernet OAM (IEEE 802.3ah) on the NodeB side

MO ParameterName

Parameter ID Setting Notes

Data Source

ETHOAM3A

H

Working

Mode

WORKMODE -- Network plan

(negotiation

not required)

Detection

Period

DTPRD -- Network plan

(negotiation

not required)

PDU Size PDUSIZE -- Network plan

(negotiation

not required)

SingleRAN




35



MO ParameterName

Parameter ID Setting Notes

Data Source

Loopback

Flag

RMTLBFLG -- Network plan

(negotiationnot required)

Fault Report

Flag

FLTINDFLG -- Network plan

(negotiation

not required)

Error Frame

Event

Duration

ERRFRMEVTPRD --- Network plan

(negotiation

not required)

Error Frame

Event

Threshold

ERRFRMEVTTHD -- Network plan

(negotiation

not required)

Error Frame

Seconds

Summary

Event

Duration

ERRFRMSCDEVTPRD -- Network plan

(negotiation

not required)

Error Frame

Seconds

Summary

Event

Threshold

ERRFRMSCDEVTTHD -- Network plan

(negotiation

not required)

NOTE


8.5.3 Precautions

None

8.5.4 Hardware Adjustment None

8.5.5 Activation


Ethernet OAM (IEEE802.3ah) using the MML and CME GUI.

SingleRAN




36



NOTE

l Enable Ethernet OAM (IEEE 802.3ah) simultaneously on the RNC side and the transmission

equipment.

l Enable Ethernet OAM (IEEE 802.3ah) simultaneously on the NodeB side and the transmission

equipment.

Using MML Commands

On the RNC side

The procedure for activating Ethernet OAM (IEEE 802.3ah) 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.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 set to appropriate values:

l Working Mode: This parameter specifies the working mode of Ethernet OAM (IEEE

802.3ah).

l Detection Period: This parameter specifies the internal at which a Protocol Data Unit

(PDU) is transmitted for fault detection.

l PDU Size: 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 defined

in IEEE 802.3ah:

–

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 Command

Examples in section 8.4.5 Activation.

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;


The RNC and NodeB support using CME single configuration to activate Ethernet OAM (IEEE

802.3ah). On the CME, set parameter listed in Table 8-6 for a NodeB. For related parameters

on the RNC side, see Table 8-3 .For detailed instructions, see CME Single Configuration

Operation Guide.

SingleRAN




37



Table 8-6 Parameters related to Ethernet OAM (IEEE 802.3ah) on the NodeB side

MO NE ParameterName

Parameter ID

ETHOAM3AH NodeB/eNodeB/eGBTS Working Mode WORKMODE

Detection Period DTPRD

PDU Size PDUSIZE

Loopback Flag RMTLBFLG

Fault Report Flag FLTINDFLG

Error Frame Event

Duration

ERRFRMEVTPRD

Error Frame EventThreshold

ERRFRMEVTTHD

Error Frame

Seconds Summary

Event Duration

ERRFRMSCDEVTPR

D

Error Frame

Seconds Summary

Event Threshold

ERRFRMSCDEVTTH

D


The RNC does not support using CME batch configuration to activate Ethernet OAM (IEEE

802.3ah), but the NodeB does. Batch reconfiguration using the CME is the recommended method

to activate a feature on existing NodeBs. This method reconfigures all data, except neighbor

relationships, for multiple NodeBs in a single procedure. The procedure is as follows:

Step 1 Choose CME > Advanced > Customize Summary Data File from the main menu of an M2000

client, or choose Advanced > Customize Summary Data File from the main menu of a CME

client, to customize a summary data file for batch reconfiguration.

NOTE

For context-sensitive help on a current task in the client, press F1.

Step 2 Export the NE data stored on the CME into the customized summary data file.

l For co-MPT multimode base stations: Choose CME > SRAN Application > MBTS

Application > Export Data > Export Base Station Bulk Configuration Data from the

main menu of the M2000 client, or choose SRAN Application > MBTS Application >

Export Data > Export Base Station Bulk Configuration Data from the main menu of the

CME client.

l For separate-MPT GSM-involved multimode base stations or GO base stations: Choose

CME > GSM Application > Export Data > eGBTS Bulk Configuration Data from the

SingleRAN




38



main menu of the M2000 client, or choose GSM Application > Export Data > Export

eGBTS Bulk Configuration Data from the main menu of the CME client.

l For separate-MPT UMTS-involved multimode base stations or UO base stations: Choose

CME > UMTS Application > Export Data > Export Base Station Bulk Configuration

Data from the main menu of the M2000 client, or choose UMTS Application > ExportData > Export Base Station Bulk Configuration Data from the main menu of the CME

client.

l For separate-MPT LTE-involved multimode base stations or LO base stations: Choose CME

> LTE Application > Export Data > Export Base Station Bulk Configuration Data from

the main menu of the M2000 client, or choose LTE Application > Export Data > Export

Base Station Bulk Configuration Data from the main menu of the CME client.

Step 3 In the summary data file, set the parameters in the MOs listed in Table 8-7 and close the file.

Table 8-7 MO related to Ethernet OAM (IEEE 802.3ah)

MO Sheet in theSummary DataFile

Parameter Group Remarks

ETHOAM3AH Transport

Maintenance Patten

Port No./Working Mode /

Loopback Flag

-

NOTE

"-" indicates that there are no remarks provided.

Step 4 Import the summary data file into the CME.


Application > Import Base Station Bulk Configuration Data from the main menu of the

M2000 client, or choose SRAN Application > MBTS Application > Import Data > Import



CME > GSM Application > Import Data > Import eGBTS Bulk Configuration Data

from the main menu of the M2000 client, or choose GSM Application > Import Data >

Import eGBTS Bulk Configuration Data from the main menu of the CME client.


CME > UMTS Application > Import Data > Import Base Station Bulk Configuration

Data from the main menu of the M2000 client, or choose UMTS Application > Import

Data > Import Base Station Bulk Configuration Data from the main menu of the CME

client.


> LTE Application > Import Data > Import Base Station Bulk Configuration Data from

the main menu of the M2000 client, or choose LTE Application > Import Data > Import


----End

SingleRAN




39




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.

8.5.7 Reconfiguration

None

8.5.8 Deactivation

Using MML Commands

On the RNC side

The procedure for deactivating Ethernet OAM (IEEE 802.3ah) using MML commands on theRNC side is the same as that on the BSC side. For details, see "On the BSC side" in Using MML

Commands in section Using MML Commands.

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 Using MML Commands.

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

SingleRAN




40



8.6.1 Requirements

Hardware

The following boards support Ethernet OAM (IEEE 802.3ah) when they are configured withEthernet ports.

NE IEEE 802.3ah

eNodeB LMPT, UMPT, UTRP2, UTRP9, or UTRPc


Protocol Requirement for TransmissionEquipment

IEEE 802.3ah The transmission equipment supports


License

Feature ID Feature Name LicenseControl Item

NE Sales Unit

LOFD-003004 Ethernet OAM Ethernet OAM eNodeB per eNodeB


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

8.6.3 Precautions

None

8.6.4 Hardware Adjustment

None

8.6.5 Activation


Ethernet OAM (IEEE802.3ah) using the MML and CME GUI.

NOTE

Enable Ethernet OAM (IEEE 802.3ah) simultaneously on the eNodeB side and the transmission equipment.

SingleRAN




41



Using MML Commands

The procedure for activating Ethernet OAM (IEEE 802.3ah) 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.5.5 Activation.


The MML command examples for activating 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.5 Activation.

Using the CME

The batch configuration using the CME on the eNodeB is the same as that on the NodeB side.

For details, see Using the CME to Perform Single Configuration and Using the CME toPerform Batch Configuration in section 8.5.5 Activation.


The activation observation using MML commands on the eNodeB side is the same as that on

the NodeB side. For details, see "On the NodeB side" in section 8.5.6 Activation

Observation.


None

8.6.8 Deactivation

Using MML Commands

On the eNodeB side

The procedure for deactivating Ethernet OAM (IEEE 802.3ah) 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.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

SingleRAN




42



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, GOUa, GOUc, or GOUd Not supported

GBTS GTMUb or UTRPc UTRPc

eGBTS UMPT UMPT



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

(IEEE802.1ag).

Ethernet OAM (ITU-T Y.1731) The transmission equipment supports Ethernet OAM

(ITU-T Y.1731).

License

No additional license is required.


Table 8-8 and Table 8-9 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-12.

Table 8-8 Data to prepare before activating Ethernet OAM (IEEE 802.1ag) or Ethernet OAM

(ITU-T Y.1731) on the BSC side

MO ParameterName

Parameter ID Setting Notes Data Source

CFMMD Subrack No. SRN

(BSC6900,

BSC6910)

-- Network plan

(negotiation not

required)

Slot No. SN

(BSC6900,

BSC6910)

-- Network plan

(negotiation not

required)

SingleRAN




43



MO ParameterName


MD Index MDIDX

(BSC6900, BSC6910)

-- Network plan


MD Level LEVEL

(BSC6900,

BSC6910)

-- Network plan

(negotiation not

required)

CFMMA MA Index MAIDX

(BSC6900,

BSC6910)

An MA index

corresponds to an MA

name. The value of the

MA Index parameter

for a CFM MD must be

unique on the BSCside. A CFM MD can

contain a maximum of

500 MAs whose

indexes range from 0 to

499.

Network plan

(negotiation not

required)

MA Name MANAME

(BSC6900,

BSC6910)

-- Network plan

(negotiation not

required)

VLAN ID VLANID

(BSC6900,

BSC6910)

If Binding VLAN is

set to YES(Yes) for a

CFM MA, do not set

VLAN ID to a VLAN

ID for other CFM MAs.

Network plan

(negotiation not

required)

CCM Send

Prid

CCMINTERVA

L

(BSC6900,

BSC6910)

-- Network plan

(negotiation not

required)

VLAN

Priority

VLANPRI

(BSC6910,

BSC6900)

This parameter is valid

only when Binding

VLAN is set to YES

(Yes) for a CFM MA.

Network plan

(negotiation not

required)

CFMME

P (for

local

MEP

configurat

ion)

Subrack No. SRN

(BSC6900,

BSC6910)

-- Network plan

(negotiation not

required)

SingleRAN




44



MO ParameterName


MA Index MAIDX

(BSC6900, BSC6910)

An MA index

corresponds to an MAname. The value of the

MA Index parameter


unique on the BSC

side. A CFM MD can


500 MAs whose


499.

Network plan


MEP Type MEPTYPE

(BSC6900, BSC6910)

Set this parameter

based on the network plan. The MEP Type

for the local MEP is set

to LocalMep

(LocalMep).

Network plan


MEP ID MEPID

(BSC6900,

BSC6910)

Set this parameter

based on the network

plan. The value of the

MEP ID parameter for

the local MEP must be

unique within an MA.

Network plan

(negotiation not

required)

Port Type PORTTYPE

(BSC6900,

BSC6910)

-- Network plan

(negotiation not

required)

Slot No. SN

(BSC6900,

BSC6910)

-- Network plan

(negotiation not

required)

Port No. PN

(BSC6900,

BSC6910)

-- Network plan

Trunk No. TRUNKN

(BSC6900,

BSC6910)

-- Network plan

(negotiation not

required)

SingleRAN




45



MO ParameterName


CFMME

P (for remote

MEP

configurat

ion)

MA Index MAIDX

(BSC6900, BSC6910)

Set this parameter

based on the network plan. An MA index

corresponds to an MA

name. The value of the

MA Index parameter


unique on the BSC

side. A CFM MD can


500 MAs whose


499.

Network plan


MEP Type MEPTYPE

(BSC6900,

BSC6910)

Set this parameter


plan. The MEP Type

for the local MEP is set

to RemoteMep

(RemoteMep).

Network plan

(negotiation not

required)

MEP ID MEPID

(BSC6900,

BSC6910)

Set this parameter




the local MEP must beunique within an MA.

Network plan

(negotiation not

required)

Port No. PN

(BSC6900,

BSC6910)

-- Network plan

(negotiation not

required)

NOTE



(ITU-T Y.1731) on the GBTS side

MO Parameter Name

Parameter ID Setting Notes DataSource

BTSETHOAM Ethernet

OAM

Type

OAMTYPE Ethernet OAM Type

can only be set to

IEEE_802_1AG

(IEEE 802.1ag), or

ITU_T_Y1731(ITU-T

Y.1731).

Network

plan

(negotiati

on not

required)

SingleRAN




46



MO Parameter Name


Monitor

Policy

MONITORPOLIC

Y


only when EthernetOAM Type is set to

ITU_T_Y1731(ITU-T

Y.1731). It is

recommended that this

parameter be set to the

default value.

Network

plan(negotiati

on not

required)

BTSETHMD Index

Type

IDTYPE Index type. Network

plan

(negotiati

on not

required)

BTS Index BTSID Index of the BTS,

uniquely identifying a

BTS in a BSC.

Network

plan

(negotiati

on not

required)

MD Name MDNAME Set this parameter



MD Name parameter

for a CFM MD must beunique on the GBTS

side.

This parameter can be

set to any value if OAM

Type is set to ITU-T Y.

1731.

Network

plan

(negotiati

on not

required)

MD Level MDLEVEL A maximum of eight

CFM MDs can be

configured on a GBTS.

The value of this

parameter ranges from

0 to 7.

Network

plan

(negotiati

on not

required)

SingleRAN




47



MO Parameter Name


BTSETHMA MD Name MDNAME Before adding a CFM

MA, add a CFM MD for the CFM MA under the

BTSETHMA MO. The

value of MD Name in

the ADD

BTSETHMA

command must be the

same as that in the ADD

BTSETHMD

command.

If OAM Type is set to

ITU-T Y.1731, replace

MEG ID with MA

Name. The value of the

MA Name parameter

must be unique within

an MEG.

Network

plan(negotiati

on not

required)

MA Name MANAME An MA is identified by

an MD name and an

MA name.


ITU-T Y.1731, replace

MEG ID with MAName. The value of the

MA Name parameter


an MEG.

Network

plan

(negotiati

on not

required)

VLAN ID VLANID Do not set VLAN ID of

a CFM MA to a VLAN

ID for other CFM MDs.

Network

plan

(negotiati

on not

required)

BTSETHLCMEP

MD Name MDNAME Before setting this parameter based on the

network plan, configure

this parameter for the

BTSETHMD MO.

Network plan

(negotiati

on not

required)

MA Name MANAME Before setting this

parameter based on the

network plan, configure

this parameter for the

BTSETHMA MO.

Network

plan

(negotiati

on not

required)

SingleRAN




48



MO Parameter Name


MEP ID MEPID Set this parameter

based on the network plan. The value of the


the local MEP must be

unique within an MA.

Network

plan(negotiati

on not

required)

BTSETHRMM

EP

MD Name MDNAME Configure this

parameter for the

BTSETHMD MO.

Network

plan

(negotiati

on not

required)

MA Name MANAME

-- Network plan

(negotiati

on not

required)

MEP ID MEPID Before checking the

continuity between a

GBTS and a remote

MEP, configure this

parameter for the

remote MEP on the

GBTS. In addition, theconfigured 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.

Network

plan

(negotiati

on not

required)

NOTE


8.7.3 Precautions

None


None

SingleRAN




49



8.7.5 Activation


Ethernet OAM (IEEE802.1ag) using the MML and CME GUI.

NOTE

l Enable Ethernet OAM (IEEE802.1ag) simultaneously on the base station and transmission equipment.

l Enable Ethernet OAM (IEEE802.1ag) simultaneously on the base station controller and transmission

equipment.

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:l MD Index

l MD Level

l MD Name

Step 2 Run the ADD CFMMA command to add an MA. In this step, set the parameters as follows:

l Set MD Index, VLAN ID, MA Index, and MA Name to appropriate values.

l Set CCM Send Prid 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 localMEP 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

local MEP and remote MEP so that the local MEP can obtain the MAC address of the

remote MEP.

On the GBTS side

Step 1 IEEE 802.1agITU-T Y.1731Run the SET BTSETHOAM command with OAM Type set to

IEEE 802.1ag or ITU-T Y.1731. If this parameter is set to ITU-T Y.1731, Monitor Policy

must be configured.

SingleRAN




50



Step 2 Run the ADD BTSETHMD command to add a CFM MD.

NOTE

When OAM Type is set to ITU-T Y.1731, MDNAME is invalid, and MEG LEVEL equals to MD LEVEL

in IEEE 802.1ag.

Step 3 Run the ADD BTSETHMA command to add an MA.

NOTE

When OAM Type is set to ITU-T Y.1731, MANAME equals to MEG ID in IEEE 802.1ag. If the GBTS

is interconnected with peer equipment, MANAME must be consistent with the MEG ID of the peer NE.

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


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


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 (IEEE802.1ag) or Ethernet OAM (ITU-TY.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

SingleRAN




51



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=5;

//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 OAM Type

Configuring Ethernet OAM (IEEE 802.1ag)

SET BTSETHOAM: OAMTYPE="EEE_802_1ag"

//Configuring Ethernet OAM (ITU-T Y.1731)

SET BTSETHOAM: OAMTYPE="ITU_T_Y1731" POLICY="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", VLANID=3;


ADD BTSETHLCMEP: IDTYPE=BYID, BTSID=7, MDNAME="CHINA", MANAME="SHANGHAI", MEPID=1,

PN=0;

//Adding a remote MEPADD 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 ",

DESTMEPID=2;

//Starting a CFM LB testCFMPING: MDNAME="CHINA", MANAME="SHANGHAI", DSTTYPE=MAC,

MAC="00E2-FC00-57B7";

//Starting an LT test

TRC BTSCFM: IDTYPE=BYID, BTSID=7, MDName="CHINA", MANAME="SHANGHAI", DESTMEPID=2;

//Starting a single-ended ETH-LM

ACT BTSETHLM: MDNAME="CHINA", MANAME="SHANGHAI", DSTTYPE=MAC, MAC="00E2-

FC00-57B7";

//Starting a two-way delay variation measurement

ACT BTSETHDM: 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.


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

On the CME, set parameters listed in Table 8-10 and Table 8-11 for a BSC and GBTS,

respectively. For related parameters on the eGBTS side, see Table 8-6. For detailed instructions,

see CME Single Configuration Operation Guide.

Table 8-10 Parameters related to Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.

1731) on the BSC side


CFMMD BSC/RNC Subrack No. SRN

Slot No. SN

SingleRAN




52




MD Name MDNAME

MD Level LEVEL

MD Index MDIDX

CFMMA MA Index MAIDX

MA Name MANAME

VLAN ID VLANID

CCM Send Prid CCMINTERVAL

VLAN Priority VLANPRI

CFMMEP Subrack No. SRN

MA Index MAIDX

MEP Type MEPTYPE

MEP ID MEPID

Port Type PORTTYPE

Slot No. SN

Port No. PN

Trunk No. TRUNKN

CFMMEP Subrack No. SRN

MA Index MAIDX

MEP Type MEPTYPE

MEP ID MEPID

Table 8-11 Parameters related to Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.

1731) on the GBTS side


BTSETHOAM GBTS OAM Type OAMTYPE

Monitor Policy MONITORPOLICY

BTSETHMD Index Type IDTYPE

BTS Index BTSID

MD Name MDNAME

SingleRAN




53




MD Level MDLEVEL

BTSETHMA MD Name MDNAME

MA Name MANAME

VLAN ID VLANID

BTSETHLCMEP MD Name MDNAME

MA Name MANAME

MEP ID MEPID

BTSETHRMMEP MD Name MDNAME

MA Name MANAME

MEP ID MEPID


Neither the BSC nor GBTS supports using CME batch configuration to activate Ethernet OAM

(IEEE 802.1ag/ITU-TY.1731), but the eGBTS does. The CME batch configuration for an

eGBTS is the same as that for a NodeB. For details, see Using the CME to Perform Batch

Configuration in section 8.8.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

SingleRAN




54



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

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.8.6 Activation 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 or der.

SingleRAN




55



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

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, MAIDX=0, MEPTYPE=RemoteMep, MEPID=11, SN=18;

//Deleting a local MEP

RMV CFMMEP: SRN=0, MAIDX=0, MEPTYPE=LocalMep, MEPID=1, PORTTYPE=ETHER, SN=18,

PN=0;

//Deleting an MA

RMV CFMMA: SRN=0, SN=18, MDIDX=0, VLANID=2, MAIDX=0, MANAME="ma0";

//Deleting an MD

RMV CFMMD: SRN=0, SN=18, MDIDX=0, LEVEL=0, MDNAME="md0";

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,

PN=0;

//Deleting an MA

RMV BTSETHMA: IDTYPE=BYID, BTSID=7, MDNAME="CHINA", MANAME="SHANGHAI", VLANID=3;

//Deleting an MD

RMV BTSETHMD: IDTYPE=BYID, BTSID=7, MDNAME="CHINA", MDLEVEL=7;

//Setting OAM Type


SET BTSETHOAM: OAMTYPE="IEEE_802_1ag"

//Configuring Ethernet OAM (ITU-T Y.1731)

SET BTSETHOAM: OAMTYPE="ITU_T_Y1731" POLICY="SA_DA_VLANID"

On the eGBTS side

SingleRAN




56



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.

8.8 Deployment of Ethernet OAM (IEEE 802.1ag) or EthernetOAM (ITU-T Y.1731) for UMTS

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


RNC FG2a, FG2c, FG2d, GOUa, GOUc, or

GOUd

Not supported

NodeB WMPT, UMPT, UTRP2, UTRP9, or

UTRPc

UMPT or UTRPc



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

(IEEE 802.1ag).

Ethernet OAM (ITU-T Y.1731) The transmission equipment supports Ethernet OAM

(ITU-T Y.1731).

License

Feature ID Feature Name License ControlItem

NE Sales Unit

WRFD-050425 Ethernet OAM EthernetOAM(per

NodeB)

NodeB per NodeB

SingleRAN




57




Common Data Preparation

Table 8-12 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-8.


(ITU-T Y.1731) on the NodeB side

MO ParameterName


GTRANSPAR

A

OAM Type OAMTYPE OAM Type can only

be set toIEEE_802_1AG

(IEEE 802.1ag) or

ITU_T_Y1731(ITU-

T Y.1731).

Network

plan(negotiation

not

required)

Monitor

Policy

MONITORPOLI

CY


only when OAM

Type is set to

ITU_T_Y1731(ITU-

T Y.1731). It is

recommended that

this parameter in the

GTRANSPARA MO

be set to the default

value.

Network

plan

(negotiation

not

required)

CFMMD MD Name MDNAME Set this parameter



MD Name parameter

for a CFM MD must

be unique on the

NodeB side.

This parameter can be

set to any value if

OAM Type is set to

ITU_T_Y1731(ITU-

T Y.1731).

Network

plan

(negotiation

not

required)

MD Level LEVEL A maximum of eight

CFM MDs can be

configured on a

NodeB. The value of

this parameter ranges

from 0 to 7.

Network

plan

(negotiation

not

required)

SingleRAN




58



MO ParameterName


CFMMA MD Name MDNAME Before adding a CFM

MA, configure this parameter for the MA

under the CFMMD

MO. The value of MD

Name in the ADD

CFMMA command

must be the same as

that in the ADD

CFMMD command.

This parameter is

invalid only when

OAM Type is set to

ITU_T_Y1731(ITU-

T Y.1731).

Network

plan(negotiation

not

required)

MA Name MANAME An MA is identified

by an MD name and an

MA name.


ITU_T_Y1731(ITU-

T Y.1731), replace

MEG ID with MA

Name. The value of

the MA Name parameter must be

unique within an

MEG.

Network

plan

(negotiation

not

required)

Binding

VLAN

BNDVLAN Set this parameter


plan. This parameter

specifies whether an

MA is bound with a

VLAN. MAs must be

bound with VLANs

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.

Network

plan

(negotiation

not

required)

SingleRAN




59



MO ParameterName


VLAN ID VLANID Set this parameter

based on the network plan. If Binding

VLAN is set to YES

(Yes) for a CFM MA,

do not set VLAN ID

to a VLAN ID for

other CFM MAs.

Network

plan(negotiation

not

required)

VLAN

Priority

VLANPRI This parameter is valid

only when Binding

VLAN is set to YES

(Yes) for a CFM MA.

Network

plan

(negotiation

not

required)

CFMMEP MD Name MDNAME Before setting this

parameter based on

the network plan,

configure this

parameter for the

CFMMD MO.

Network

plan

(negotiation

not

required)


parameter based on

the network plan,

configure this parameter for the

CFMMA MO.

Network

plan

(negotiation

notrequired)

MEP ID MEPID Set this parameter



MEP ID parameter

for the local MEP


an MA.

Network

plan

(negotiation

not

required)

CFMRMEP MD Name MDNAME Before setting this parameter based on

the network plan,

configure this

parameter for the

CFMMD MO.

Network plan

(negotiation

not

required)


parameter based on

the network plan,

configure this

parameter for the

CFMMA MO.

Network

plan

(negotiation

not

required)

SingleRAN




60



MO ParameterName


RMEP ID RMEPID Before checking the

continuity between a NodeB and a remote

MEP, configure this

parameter for the

remote MEP on the

NodeB side. 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.

Network

plan(negotiation

not

required)

MAC

Address

MAC The MAC address

must be a unicast

address. The MAC

address of the remote

MEP is obtained from

the CCM message. If

the MAC address

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, usedifferent MAC

addresses for these

remote MEPs.

Otherwise, the CFM

LB test may become

abnormal.

Network

plan

(negotiation

not

required)

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

SingleRAN




61



in the CFMMEP MO is activated in the summary data file. Table 8-13 lists the parameters

related to the route interlock function.

Table 8-13 Parameters related to the route interlock function

NE MO ParameterName

ParameterID

DataSource

Setting Notes

NodeB CFMBNDIP MD Name MDNAME Before

setting this

parameter

based on the

network

plan,

configure

this

parameter for the

CFMMD

MO.

Network

plan

(negotiation

not required)

MA Name MANAME Before

setting this

parameter

based on the

network

plan,

configure

this parameter

for the

CFMMA

MO.

Network

plan

(negotiation

not required)

RMEP ID RMEPID Before

setting this

parameter

based on the

network

plan,

configure

this

parameter

for the

CFMRMEP

MO.

Network

plan

(negotiation

not required)

SingleRAN




62



NE MO ParameterName

ParameterID

DataSource

Setting Notes

IP Address BNDIP Set this

parameter based on the

network

plan. This

parameter

specifies the

IP address of

the Ethernet

port or the

Ethernet link

aggregation

group

correspondin

g to the

remote MEP.

l Do not

perform

route

interlock

to the

active

and

standby

IP routes by using

CFM and

bidirectio

nal

forwardi

ng

detection

(BFD).

l Do not

bind two

remoteMEPs in

an MA to

the same

IP

address.

The

bound IP

address

must be

different

from that

Network

plan(negotiation

not required)

SingleRAN




63



NE MO ParameterName

ParameterID

DataSource

Setting Notes

of all

configured or

working

ports

(includin

g

physical

ports and

loopback

ports) on

the local

equipme

nt.

RNC None None None None None

8.8.3 Precautions

None


None

8.8.5 Activation

Using MML Commands

On the RNC side

The procedure for activating 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 section 8.7.5 Activation.

On the NodeB side

Step 1 Run the SET ETHOAM command with 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 CFMMD command to add a CFM MD.

NOTE

When OAM Type is set to ITU-T Y.1731, MDNAME is invalid, and MEG LEVEL equals to MD LEVEL

in IEEE 802.1ag.

Step 3 Run the ADD CFMMA command to add an MA.

SingleRAN




64



NOTE

When OAM Type is set to ITU-T Y.1731, MANAME equals to MEG ID in IEEE 802.1ag. If the GBTS

is interconnected with peer equipment, MANAME must be consistent with the MEG ID of the peer NE.

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 a CFM binding IP address of the remote MEP to

implement the route interlock.

----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. Duringthe implementation of the MAC PING test, ensure that the CC function is enabled at the


remote MEP.

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 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 ETHLM command to activate the single-ended ETH-LM function at a

specified local MEP.l Run the ACT ETHDM command to activate the two-way delay variation measurement

function at a specified local MEP.


On the RNC side


(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

//Setting OAM Type


SET ETHOAM: OAMTYPE="IEEE_802_1ag"

Configuring Ethernet OAM (ITU-T Y.1731)

SET ETHOAM: OAMTYPE="ITU_T_Y1731" POLICY="SA_DA_VLANID"

//Adding a CFM MD

ADD CFMMD: MDNAME="CHINA", LEVEL=7;

//Adding a CFM MA

ADD CFMMA: MDNAME="CHINA", MANAME="SHANGHAI", CN=0, SRN=0, SN=6, BNDVLAN=YES,

VLANID=3;


ADD CFMMEP: MDNAME="CHINA", MANAME="SHANGHAI", MEPID=1000, CN=0, SRN=0, SN=6,

SBT=BASE_BOARD, PT=ETH, PN=0;

//Adding a remote MEPADD CFMRMEP: MDNAME="CHINA", MANAME="SHANGHAI", RMEPID=2000, MAC="0023-8956-7895";

SingleRAN




65



//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", DSTTYPE=MAC, MAC="00E2-FC00-57B7";

//Starting a two-way delay variation measurementACT ETHDM: MDNAME="CHINA", MANAME="SHANGHAI", DSTTYPE=MAC, MAC="00E2-FC00-57B7";


The RNC and NodeB support using the CME single configuration to activate Ethernet OAM

(IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731).

On the CME, set parameters according to Table 8-15 on the NodeB. The parameters on the RNC

are the same as those on the BSC. For details, see Table 8-11. For detailed instructions, see

CME Single Configuration Operation Guide.

Table 8-14 Parameters related to Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731) on the NodeB side

MO NE ParameterName

Parameter ID

GTRANSPARA NodeB/eNodeB/eGBTS OAM Type OAMTYPE

Monitor Policy MONITORPOLICY

CFMMD MD Name MDNAME

MD Level LEVEL

CFMMA MD Name MDNAME

MA Name MANAME

Binding VLAN BNDVLAN

VLAN ID VLANID

VLAN Priority VLANPRI

CFMMEP MD Name MDNAME

MEP ID MEPID

Port No. PN

CFMRMEP MD Name MDNAME

RMEP ID RMEPID

MAC Address MAC

SingleRAN




66




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.

Step 1 Choose CME > Advanced > Customize Summary Data File from the main menu of an M2000client, or choose Advanced > Customize Summary Data File from the main menu of a CME

client, to customize a summary data file for batch reconfiguration.

NOTE

For context-sensitive help on a current task in the client, press F1.

Step 2 Export the NE data stored on the CME into the customized summary data file.


Application > Export Data > Export Base Station Bulk Configuration Data from the

main menu of the M2000 client, or choose SRAN Application > MBTS Application >

Export Data > Export Base Station Bulk Configuration Data from the main menu of the

CME client.


CME > GSM Application > Export Data > eGBTS Bulk Configuration Data from the

main menu of the M2000 client, or choose GSM Application > Export Data > Export

eGBTS Bulk Configuration Data from the main menu of the CME client.


CME > UMTS Application > Export Data > Export Base Station Bulk Configuration

Data from the main menu of the M2000 client, or choose UMTS Application > Export

Data > Export Base Station Bulk Configuration Data from the main menu of the CME

client.

l For separate-MPT LTE-involved multimode base stations or LO base stations: Choose CME> LTE Application > Export Data > Export Base Station Bulk Configuration Data from

the main menu of the M2000 client, or choose LTE Application > Export Data > Export


Step 3 Set the parameters in the MOs listed in Table 8-16 and close the summary data file.

Table 8-15 Common MOs related to Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T

Y.1731)

MO Sheet in the SummaryData File

Parameter Group Setting

Notes

GTRANSPARA Transport Maintenance Patten Ethernet OAM Type/

Monitor Policy

-

CFMMD Transport Maintenance Patten MD Name/MD Level -

CFMMA Transport Maintenance Patten MD Name/MA Name/

Binding VLAN/VLAN ID/

VLAN Priority

-

SingleRAN




67




Parameter Group Setting Notes

CFMMEP Transport Maintenance Patten MD Name/MA Name/MEPID/Port Type/Port No./CC

Switch

-

CFMRMEP Transport Maintenance Patten MD Name/MA Name/RMEP

ID/MAC Address

-

NOTE

"-" indicates that there are no remarks provided.

Table 8-16 Scenario-specific MO related to Ethernet OAM (IEEE 802.1ag) or Ethernet OAM

(ITU-T Y.1731)


Parameter Group Setting Notes

CFMBNDIP Transport Maintenance Patten MD Name/MA Name/

RMEP ID/IP Address

-

Step 4 Import the summary data file into the CME.

l For co-MPT multimode base stations: Choose CME > SRAN Application > MBTSApplication > Import Base Station Bulk Configuration Data from the main menu of the

M2000 client, or choose SRAN Application > MBTS Application > Import Data > Import



CME > GSM Application > Import Data > Import eGBTS Bulk Configuration Data

from the main menu of the M2000 client, or choose GSM Application > Import Data >

Import eGBTS Bulk Configuration Data from the main menu of the CME client.


CME > UMTS Application > Import Data > Import Base Station Bulk Configuration

Data from the main menu of the M2000 client, or choose UMTS Application > Import

Data > Import Base Station Bulk Configuration Data from the main menu of the CME

client.


> LTE Application > Import Data > Import Base Station Bulk Configuration Data from

the main menu of the M2000 client, or choose LTE Application > Import Data > Import


----End

SingleRAN




68




Using MML Commands

On the RNC 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,


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

Before using methods 1 and 2, ensure that the CC function is enabled at the local and remote

ends.

Method 1: Run the DSP CFMRMEP command to query the status and MAC address of the

remote MEP. If value of the Actual MAC Address is that of the remote port and the value of

Status is Normal, the remote MEP is in normal state and Ethernet OAM (IEEE 802.1ag) or

Ethernet OAM (ITU-T Y.1731) has been activated.

Method 2: Run the CFMPING or CFMTRACE command to start an LB or LT test from thelocal MEP to the remote RMEP. If the MAC address of the remote MEP is pinged through,


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.

Before using method 3, you do not need to enable the CC function.

Method 3: If you have obtained the MAC address of the remote MEP, run the CFMPING or

CFMTRACE command to check the continuity between the local MEP and the remote MEP.


If the base station supports IEEE 802.1ag or ITU-T Y.1731 and you need to change the

configuration of Ethernet OAM (IEEE 802.1ag) to the configuration of Ethernet OAM (ITU-T

Y.1731), you must delete the configured MDs, MAs, MEPs, and RMEPs for Ethernet OAM

(IEEE 802.1ag) first.

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

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.


SingleRAN




69






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 OAM Type set to ITU_T_Y1731(ITU-T Y.1731).

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.

----End

8.8.8 Deactivation

This feature can be deactivated by deleting all configurations in reverse order.

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 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.8 Deactivation.

On the NodeB 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.





----End

MML Command ExamplesOn 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.8 Deactivation.

On the NodeB side


RMV CFMRMEP: MDNAME="CHINA", MANAME="SHANGHAI", RMEPID=2000, MAC="0023-8956-7895";


RMV CFMMEP: MDNAME="CHINA", MANAME="SHANGHAI", MEPID=1000, CN=0, SRN=0, SN=6,SBT=BASE_BOARD, PT=ETH, PN=0;

SingleRAN




70



//Deleting a CFM MA

RMV CFMMA: MDNAME="CHINA", MANAME="SHANGHAI", CN=0, SRN=0, SN=6, BNDVLAN=YES,

VLANID=3;

//Deleting a CFM MD

RMV CFMMD: MDNAME="CHINA", LEVEL=7;

//Setting OAM Type

Changing the configuration of Ethernet OAM (ITU-T Y.1731) to the configuration of

Ethernet OAM (IEEE 802.1ag)

SET ETHOAM: OAMTYPE="IEEE_802_1ag"

Changing the configuration of Ethernet OAM (IEEE 802.1ag) to the configuration of

Ethernet OAM (ITU-T Y.1731)

SET ETHOAM: OAMTYPE="ITU_T_Y1731" POLICY="SA_DA_VLANID"

8.9 Deployment of Ethernet OAM (IEEE 802.1ag) or Ethernet

OAM (ITU-T Y.1731) for LTE

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


eNodeB LMPT, UMPT, UTRP2, UTRP9, or

UTRPc

LMPT, UMPT, or UTRPc



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

OAM (IEEE 802.1ag).

Ethernet OAM (ITU-T Y.1731) The transmission equipment supports Ethernet

OAM (ITU-T Y.1731).

License

Feature ID Feature Name LicenseControl Item

NE Sales Units

LOFD-003004 Ethernet OAM Ethernet OAM eNodeB per eNodeB

SingleRAN




71




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

8.9.3 Precautions

None


None

8.9.5 Activation

Using MML Commands

The procedure for activating Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.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.



(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.5 Activation.

Using the CME

The CME configuration on the eNodeB side is the same as that on the NodeB side. For details,

see Using the CME to Perform Single Configuration and Using the CME to Perform Batch

Configuration in section 8.8.5 Activation.


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.

SingleRAN




72



8.9.8 Deactivation

Using MML Commands

The procedure for deactivating Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.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.



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.

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 delay

ETH-DM, and delay variation measurement in real time. You can obtain the values of the

following counters from the real-time monitoring interface:

l ITU-T Y.1731 single-ended ETH-LM

– 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

l ITU-T Y.1731 two-way ETH-DM and delay variation measurement

– Average delay

– Average delay variation

8.11 Parameter Optimization

None

8.12 Troubleshooting 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 alarm 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, if the remote loopback succeeds,

ALM-21374 ETHOAM 3AH Remote Loopback is reported due to service congestion. This

alarm is cleared when the remote loopback test ends.

On the NodeB, eNodeB, or eGBTS side

SingleRAN




73



If Ethernet OAM (IEEE 802.3ah) fails, check whether the alarms listed in Table 8-18 are

reported. If yes, clear these alarms following the steps provided in handling suggestions.

Table 8-17 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

generated 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-18. The Ethernet trunk group and ALM-25895 Ethernet Trunk Group Fault are

supported by macro base stations only.

Table 8-18 Alarms related to Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731)

Alarm ID Alarm Name AlarmSeverity

25880 Ethernet Link Fault

In SRAN7.0, this alarm is reported with the only cause value

"Ethernet Link Fault".In SRAN 8.0, the following cause values are added to this

alarm:

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.

Major

SingleRAN




74



Alarm ID Alarm Name AlarmSeverity

25895 Ethernet Trunk Group Fault

In SRAN 7.0, this alarm is reported with no cause value.

In SRAN 8.0, the following cause values are added to this

alarm:

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.

Major

On the GBTS side

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

SingleRAN




75



9 Parameters

Table 9-1 Parameter description

Parameter ID NE MMLCommand

Feature ID Feature Name Description

MDNAME BTS3900 ADD CFMMD

DSP CFMMD

RMV CFMMD

LST CFMMD

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the name

of the CFM MD.

GUI Value

Range:1~43

characters

Unit:None

Actual Value

Range:1~43

characters

Default

Value:None

LEVEL BTS3900 ADD CFMMD

DSP CFMMD

DSP CFMMA

DSP CFMMEP

DSPCFMRMEP

LST CFMMD

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the level of

the CFM MD.

GUI Value

Range:0~7

Unit:None

Actual Value

Range:0~7

Default Value:0

SingleRAN

Ethernet OAM Feature Parameter Description 9 Parameters



76





SRN BSC6900 ADD CFMMD

RMV CFMMD

WRFD-050402

WRFD-050409

WRFD-050410

WRFD-140207

WRFD-140208

WRFD-050425

IP Transmission

Introduction onIub Interface

IP Transmission

Introduction on

Iu Interface

IP Transmission

Introduction on

Iur Interface

Iu/Iur

Transmission

Resource Pool

in RNC

Iub

Transmission

Resource Pool

in RNC

Ethernet OAM

Meaning:The

subrack number for running this

command

GUI Value

Range:0~11

Unit:None

Actual Value

Range:0~11

Default

Value:None

SRN BSC6910 ADD CFMMD

RMV CFMMD

WRFD-150243

WRFD-150244

WRFD-050425

Iub IP

Transmission

Based on

Dynamic Load

Balance

Iu/Iur IP

Transmission

Based on

Dynamic Load

Balance

Ethernet OAM

Meaning:The

subrack number

for running this

command

GUI Value

Range:0~11

Unit:None

Actual Value

Range:0~11

Default

Value:None

SingleRAN




77





SN BSC6900 ADD CFMMD

RMV CFMMD

WRFD-050402

WRFD-050409

WRFD-050410

WRFD-140207

WRFD-140208

WRFD-050425

IP Transmission

Introduction onIub Interface

IP Transmission

Introduction on

Iu Interface

IP Transmission

Introduction on

Iur Interface

Iu/Iur

Transmission

Resource Pool

in RNC

Iub

Transmission

Resource Pool

in RNC

Ethernet OAM

Meaning:Indi-

cates the slotnumber for

running this

command

GUI Value

Range:

0~5;8~27

Unit:None

Actual Value

Range:0~5,

8~27

Default

Value:None

SN BSC6910 ADD CFMMD

RMV CFMMD

WRFD-150243

WRFD-150244

WRFD-050425

Iub IP

Transmission

Based on

Dynamic Load

Balance

Iu/Iur IP

Transmission

Based on

Dynamic Load

Balance

Ethernet OAM

Meaning:Indi-

cates the slot

number for

running this

command

GUI Value

Range:0~27

Unit:None

Actual Value

Range:0~27

Default

Value:None

MDIDX BSC6900 ADD CFMMD

RMV CFMMD

WRFD-050425 Ethernet OAM Meaning:Identi-

fies a

maintenance

domain

GUI Value

Range:0~7

Unit:None

Actual Value

Range:0~7

Default

Value:None

SingleRAN




78





MDIDX BSC6910 ADD CFMMD

RMV CFMMD


fies amaintenance

domain

GUI Value

Range:0~7

Unit:None

Actual Value

Range:0~7

Default

Value:None

Level BSC6900 ADD CFMMD WRFD-050425 Ethernet OAM Meaning:Classof the

maintenance

domain

GUI Value

Range:0~7

Unit:None

Actual Value

Range:0~7

Default Value:0

Level BSC6910 ADD CFMMD WRFD-050425 Ethernet OAM Meaning:Class

of the

maintenance

domain

GUI Value

Range:0~7

Unit:None

Actual Value

Range:0~7

Default Value:0

SingleRAN




79





MAIDX BSC6900 ADD CFMMA

RMV CFMMA


fies amaintenance

group.

Maintenance

group:

maintenance

alliance (MA),

which is a

component of

the maintenance

domain (MD).

One MD can be

divided into one

or more

maintenance

groups. 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 activeand standby

FG2c or GOUc

boards. The

range of the

independent

board is the

same as the

range of active

and standby

boards.

GUI ValueRange:0~499

Unit:None

Actual Value

Range:0~499

Default

Value:None

SingleRAN




80





MAIDX BSC6910 ADD CFMMA

RMV CFMMA


fies amaintenance

group.

Maintenance

group:

maintenance

alliance (MA),

which is a

component of

the maintenance

domain (MD).

One MD can be

divided into one

or more

maintenance

groups. The

range of the MA

index is 0~499

for one pair of

active and

standby FG2c or

GOUc boards.

The range of the

independent board is the

same as the

range of active

and standby

boards.

GUI Value

Range:0~2999

Unit:None

Actual Value

Range:0~2999

Default

Value:None

SingleRAN




81





MANAME BSC6900 ADD CFMMA WRFD-050425 Ethernet OAM Meaning:Name

of the MAGUI Value

Range:1~20

characters

Unit:None

Actual Value

Range:1~20

characters

Default

Value:None

MANAME BSC6910 ADD CFMMA WRFD-050425 Ethernet OAM Meaning:Nameof the MA

GUI Value

Range:1~20

characters

Unit:None

Actual Value

Range:1~20

characters

Default

Value:None

SingleRAN




82





VLANID BSC6900 ADD CFMMA WRFD-050425 Ethernet OAM Meaning:Speci-

fies theidentifier of a

VLAN.

Connectivity

Fault

Management

(CFM) supports

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

GUI Value

Range:2~4094

Unit:None

Actual ValueRange:2~4094

Default

Value:None

SingleRAN




83





VLANID BSC6910 ADD CFMMA WRFD-050425 Ethernet OAM Meaning:Speci-

fies theidentifier of a

VLAN.

Connectivity

Fault

Management

(CFM) supports

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

GUI Value

Range:2~4094

Unit:None


Default

Value:None

CCMINTERVA

L

BSC6900 ADD CFMMA WRFD-050425 Ethernet OAM Meaning:Trans-

mission period

of the CCM

packet in the

MA

GUI Value

Range:10, 100,1000

Unit:ms

Actual Value

Range:10, 100,

1000

Default Value:

1000

SingleRAN




84





CCMINTERVA

L

BSC6910 ADD CFMMA WRFD-050425 Ethernet OAM Meaning:Trans-

mission periodof the CCM

packet in the

MA

GUI Value

Range:10, 100,

1000

Unit:ms

Actual Value

Range:10, 100,

1000

Default Value:

1000

VLANPRI BSC6910 ADD CFMMA WRFD-050424 Traffic Priority

Mapping onto

Transmission

Resources

Meaning:Priorit

y of the VLAN.

The VLAN

priority is used

to prioritize

packets at the

data link layer in

an Ethernet. 0

indicates thelowest priority.

7 indicates the

highest priority.

The high-

priority packets

are

preferentially

transmitted

during

congestion of

links.

GUI Value

Range:0~7

Unit:None

Actual Value

Range:0~7

Default Value:6

SingleRAN




85





VLANPRI BSC6900 ADD CFMMA WRFD-050424 Traffic Priority

Mapping ontoTransmission

Resources

Meaning:Priorit

y of the VLAN.The VLAN

priority is used

to prioritize

packets at the

data link layer in

an Ethernet. 0

indicates the

lowest priority.

7 indicates the

highest priority.

The high-

priority packets

are

preferentially

transmitted

during

congestion of

links.

GUI Value

Range:0~7

Unit:None


Default Value:6

SRN BSC6900 ADD CFMMEP

RMV CFMMEP

MRFD-210301 Configuration

Management

Meaning:Numb

er of the subrack

GUI Value

Range:0~11

Unit:None

Actual Value

Range:0~11

Default

Value:None

SingleRAN




86





SRN BSC6910 ADD CFMMEP

RMV CFMMEP

MRFD-210301 Configuration

Management

Meaning:Numb

er of the subrack GUI Value

Range:0~11

Unit:None

Actual Value

Range:0~11

Default

Value:None

SingleRAN




87





MAIDX BSC6900 ADD CFMMEP

RMV CFMMEP


fies amaintenance

group.

Maintenance

group:

maintenance

alliance (MA),

which is a

component of

the maintenance

domain (MD).

One MD can be

divided into one

or more

maintenance

groups. 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 activeand standby

FG2c or GOUc

boards. The

range of the

independent

board is the

same as the

range of active

and standby

boards.

GUI ValueRange:0~499

Unit:None

Actual Value

Range:0~499

Default

Value:None

SingleRAN




88





MAIDX BSC6910 ADD CFMMEP

RMV CFMMEP


fies amaintenance

group.

Maintenance

group:

maintenance

alliance (MA),

which is a

component of

the maintenance

domain (MD).

One MD can be

divided into one

or more

maintenance

groups. The

range of the MA

index is 0~499

for one pair of

active and

standby FG2c or

GOUc boards.

The range of the

independent board is the

same as the

range of active

and standby

boards.

GUI Value

Range:0~2999

Unit:None

Actual Value

Range:0~2999

Default

Value:None

SingleRAN




89





MEPTYPE BSC6900 ADD CFMMEP WRFD-050425 Ethernet OAM Meaning:The

type of themaintenance

point added to

the maintenance

group.

LocalMep

indicates a local

maintenance

point and

RemoteMep

indicates a

remote

maintenance

point.

GUI Value

Range:LocalMe

p(LocalMep),

RemoteMep

(RemoteMep)

Unit:None

Actual Value

Range:LocalMe

p, RemoteMepDefault

Value:None

SingleRAN




90





MEPTYPE BSC6910 ADD CFMMEP WRFD-050425 Ethernet OAM Meaning:The

type of themaintenance

point added to

the maintenance

group.

LocalMep

indicates a local

maintenance

point and

RemoteMep

indicates a

remote

maintenance

point.

GUI Value

Range:LocalMe

p(LocalMep),

RemoteMep

(RemoteMep)

Unit:None

Actual Value

Range:LocalMe

p, RemoteMepDefault

Value:None

MEPID BSC6900 ADD CFMMEP

RMV CFMMEP


fies a

maintenance

point in the

maintenance

alliance. A

maintenance

point is an edge

node of the MA.

GUI Value

Range:1~1000

Unit:None

Actual Value

Range:1~1000

Default

Value:None

SingleRAN




91





MEPID BSC6910 ADD CFMMEP

RMV CFMMEP


fies amaintenance

point in the

maintenance

alliance. A

maintenance

point is an edge

node of the MA.

GUI Value

Range:1~3000

Unit:None


Default

Value:None

PORTTYPE BSC6900 ADD CFMMEP WRFD-050425 Ethernet OAM Meaning:Indi-

cates the type of

the physical

port . ETHER

indicates the

ethernet port and

TRUNK indicates the

aggregation

group.

GUI Value

Range:ETHER,

TRUNK

Unit:None

Actual Value

Range:ETHER,

TRUNK

Default

Value:None

SingleRAN




92





PORTTYPE BSC6910 ADD CFMMEP WRFD-050425 Ethernet OAM Meaning:Indi-

cates the type of the physical

port . ETHER

indicates the

ethernet port and

TRUNK

indicates the

aggregation

group.

GUI Value

Range:ETHER,

TRUNK

Unit:None

Actual Value

Range:ETHER,

TRUNK

Default

Value:None

SN BSC6900 ADD CFMMEP

RMV CFMMEP

WRFD-050402

WRFD-050409

WRFD-050410

WRFD-140207

WRFD-140208

WRFD-050425

IP Transmission

Introduction on

Iub Interface

IP TransmissionIntroduction on

Iu Interface

IP Transmission

Introduction on

Iur Interface

Iu/Iur

Transmission

Resource Pool

in RNC

IubTransmission

Resource Pool

in RNC

Ethernet OAM

Meaning:Indi-

cates the slot

number for

running thiscommand

GUI Value

Range:

0~5;8~27

Unit:None

Actual Value

Range:0~5,

8~27

Default

Value:None

SingleRAN




93





SN BSC6910 ADD CFMMEP

RMV CFMMEP

WRFD-150243

WRFD-150244

WRFD-050425

Iub IP

TransmissionBased on

Dynamic Load

Balance

Iu/Iur IP

Transmission

Based on

Dynamic Load

Balance

Ethernet OAM

Meaning:Indi-

cates the slotnumber for

running this

command

GUI Value

Range:0~27

Unit:None

Actual Value

Range:0~27

Default

Value:None

PN BSC6900 ADD CFMMEP WRFD-050425 Ethernet OAM Meaning:Speci-

fies Ethernet

port number.

GUI Value

Range:0~11

Unit:None

Actual Value

Range:0~7

(FG2a), 0~1

(GOUa), 0~11(FG2c), 0~3

(GOUc)

Default

Value:None

PN BSC6910 ADD CFMMEP WRFD-050425 Ethernet OAM Meaning:Speci-

fies Ethernet

port number.

GUI Value

Range:0~11

Unit:NoneActual Value

Range:0~11

(FG2c), 0~3

(GOUc)

Default

Value:None

SingleRAN




94





TRUNKN BSC6900 ADD CFMMEP WRFD-050425 Ethernet OAM Meaning:TRUN

K groupnumber.

GUI Value

Range:0~11

Unit:None

Actual Value

Range:0~11

Default

Value:None

TRUNKN BSC6910 ADD CFMMEP WRFD-050425 Ethernet OAM Meaning:TRUN

K groupnumber.

GUI Value

Range:0~11

Unit:None

Actual Value

Range:0~11

Default

Value:None

SingleRAN




95





OAMTYPE BTS3900 SET ETHOAM

LST ETHOAM

LOFD-0030040

2 /TDLOFD-0030

0402

LOFD-0030040

3 /

TDLOFD-0030

0403

GBFD-118630

Ethernet OAM

(IEEE 802.1ag)Ethernet OAM

(Y.1731)

Meaning:Indi-

cates the type of Ethernet

OAM.The

current Ethernet

OAM type

includes IEEE

802.1ag or ITU-

T Y.1731

ETHOAM.

GUI Value

Range:IEEE_80

2_1AG(IEEE

802.1ag),

ITU_T_Y1731

(ITU-T Y.1731)

Unit:None

Actual Value

Range:IEEE_80

2_1AG,

ITU_T_Y1731

Default

Value:IEEE_80

2_1AG(IEEE802.1ag)

SingleRAN




96





MONITORPOL

ICY

BTS3900 SET ETHOAM

LST ETHOAM

LOFD-0030040

3 /TDLOFD-0030

0403

GBFD-118630

Ethernet OAM

(Y.1731)

Meaning:Indi-

cates the ITU-TY.1731

monitoring

policy.The

monitor policy

includes the

following

values:

PORTID_VLA

NID (based on

PortID and

VLANID),

PORTID_VLA

NID_VLANPRI

(based on

PortID,

VLANID, and

VLAN PRI),

SA_DA_VLAN

ID (based on

PortID, source

MAC address,

destination

MAC address,and VLANID),

SA_DA_VLAN

ID_VLANPRI

(based on

PortID, source

MAC address,

destination

MAC address,

VLANID, and

VLAN PRI),

and SA_DA

(based on

PortID, source

MAC address,

and destination

MAC address).

GUI Value

Range:PORTID

_VLANID

(Based on

PortID and

VLANID),

SingleRAN




97





PORTID_VLA

NID_VLANPRI(Based on

PortID,VLANI

D and VLAN

PRI),

SA_DA_VLAN

ID(Based on

SA,DA and

VLANID),

SA_DA_VLAN

ID_VLANPRI

(Based on

SA,DA,VLANI

D and VLAN

PRI), SA_DA

(Based on SA

and DA)

Unit:None

Actual Value

Range:PORTID

_VLANID,

PORTID_VLA

NID_VLANPRI

,

SA_DA_VLAN

ID,

SA_DA_VLAN

ID_VLANPRI,

SA_DA

Default

Value:PORTID

_VLANID_VL

ANPRI(Based

on

PortID,VLANI

D and VLAN

PRI)

SingleRAN




98





MDNAME BTS3900 ADD CFMMA

DSP CFMMA

MOD CFMMA

RMV CFMMA

LST CFMMA

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the nameof the MD to

which the MA

belongs.

GUI Value

Range:1~43

characters

Unit:None

Actual Value

Range:1~43

characters

Default

Value:None

MANAME BTS3900 ADD CFMMA

DSP CFMMA

MOD CFMMA

RMV CFMMA

LST CFMMA

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the name

of the MA.

GUI Value

Range:1~43

characters

Unit:None


characters

Default

Value:None

BNDVLAN BTS3900 ADD CFMMA

DSP CFMMA

LST CFMMA

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates whether

the MA is

associated with

the VLAN.

GUI Value

Range:NO(No),

YES(Yes)

Unit:None

Actual Value

Range:NO, YES

Default

Value:YES

(Yes)

SingleRAN




99





VLANID BTS3900 ADD CFMMA

DSP CFMMA

LST CFMMA

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the ID of the VLAN with

which the MA is

associated.

GUI Value

Range:1~4094

Unit:None

Actual Value

Range:1~4094

Default Value:1

VLANPRI BTS3900 ADD CFMMA

MOD CFMMA

DSP CFMMA

LST CFMMA

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-cates the priority

of the VLAN

with which the

MA is

associated.

GUI Value

Range:0~7

Unit:None

Actual Value

Range:0~7Default Value:0

MDNAME BTS3900 ACT CFMCC

ACT ETHDM

ACT ETHLM

ADD CFMMEP

DEA CFMCC

DSP CFMMEP

RMV CFMMEP

LST CFMMEP

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the name

of the MD to

which the MEP

belongs.

GUI Value

Range:1~43

characters


Range:1~43

characters

Default

Value:None

SingleRAN




100





MANAME BTS3900 ACT CFMCC

ACT ETHDM

ACT ETHLM

ADD CFMMEP

DEA CFMCC

DSP CFMMEP

RMV CFMMEP

LST CFMMEP

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the nameof the MA to

which the MEP

belongs.

GUI Value

Range:1~43

characters

Unit:None

Actual Value

Range:1~43

characters

Default

Value:None

MEPID BTS3900 ACT CFMCC

ACT ETHDM

ACT ETHLM

ADD CFMMEP

DEA CFMCC

DSP CFMMEP

RMV CFMMEPDSP ETHDM

DSP ETHLM

LST CFMMEP

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the MEP

ID.

GUI Value

Range:1~8191

Unit:None

Actual Value

Range:1~8191Default

Value:None

MDNAME BTS3900 ADD

CFMRMEP

DSP

CFMRMEP

RMV

CFMRMEP

LST

CFMRMEP

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the name

of the MD to

which the

RMEP belongs.

GUI Value

Range:1~43characters

Unit:None

Actual Value

Range:1~43

characters

Default

Value:None

SingleRAN




101





MANAME BTS3900 ADD

CFMRMEPDSP

CFMRMEP

RMV

CFMRMEP

LST

CFMRMEP

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the nameof the MA to

which the

RMEP belongs.

GUI Value

Range:1~43

characters

Unit:None

Actual Value

Range:1~43

characters

Default

Value:None

RMEPID BTS3900 ACT ETHDM

ACT ETHLM

ADD

CFMRMEP

DSP

CFMRMEP

RMV

CFMRMEP

DSP ETHDM

DSP ETHLM

LST

CFMRMEP

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the RMEP

ID.

GUI Value

Range:1~8191

Unit:None

Actual Value

Range:1~8191Default

Value:None

SingleRAN




102





MAC BTS3900 ADD

CFMRMEPDSP

CFMRMEP

LST

CFMRMEP

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the MACaddress of the

RMEP. It must

be a valid

unicast address

in the format of

XXXX-XXXX-

XXXX. The

MAC address of

the RMEP can

be obtained

from the MAC

address field

carried in the

CCM message.

If the MAC

address

configured by

the user is

different from

that carried in

the CCM

message, the

MAC addresscarried in the

MAC message

prevails.

GUI Value

Range:14

characters

Unit:None

Actual Value

Range:14

characters

Default Value:

0000-0000-000

0

SingleRAN




103





MDNAME BTS3900 ADD

CFMBNDIPRMV

CFMBNDIP

LST

CFMBNDIP

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the nameof the MD to

which the

RMEP belongs.

GUI Value

Range:1~43

characters

Unit:None

Actual Value

Range:1~43

characters

Default

Value:None

MANAME BTS3900 ADD

CFMBNDIP

RMV

CFMBNDIP

LST

CFMBNDIP

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the name

of the MA to

which the

RMEP belongs.

GUI Value

Range:1~43

characters

Unit:None

Actual Value

Range:1~43

characters

Default

Value:None

RMEPID BTS3900 ADD

CFMBNDIP

RMV

CFMBNDIP

LST

CFMBNDIP

WRFD-050425

LOFD-0030040

2 /

TDLOFD-00300402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the RMEP

ID.

GUI Value

Range:1~8191

Unit:None

Actual Value

Range:1~8191

Default

Value:None

SingleRAN




104





BNDIP BTS3900 ADD

CFMBNDIPRMV

CFMBNDIP

LST

CFMBNDIP

WRFD-050425

LOFD-0030040

2 /

TDLOFD-0030

0402

GBFD-118630

Ethernet OAM

Ethernet OAM

(IEEE 802.1ag)

Meaning:Indi-

cates the IPaddress of the

Ethernet port or

Ethernet trunk

corresponding

to an RMEP.

The binding IP

address must be

different from

the existing

local IP address

or the IP address

of any effective

port (including

the physical port

and loopback

port). The

binding IP

address must be

different from

the local IP

address

dynamically

negotiated onthe PPP or

MLPPP link.

During the

binding of an IP

address, an error

messaged

indicating IP

address conflicts

may be

displayed. In

this case, list the

existing IP

address in the

system that

conflicts with

the IP address to

be bound by

running the

related MML

commands.

Then, manually

resolve the IP

address

SingleRAN




105





conflicts. To list

the device IPaddress, 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. To list

the local IP

address of the

MLPPP group,

run the LST

MPGRP or DSPMPGRP

command. To

list the IP

address of the

local

maintenance

channel, run the

LST LOCALIP

or DSP

LOCALIP. To

list the next hop

IP address of the

route, run the

LST IPRT or

DSP IPRT

command.

GUI Value

Range:Valid IP

address

Unit:None

SingleRAN




106





Actual Value

Range:Valid IPaddress

Default

Value:None

PN BTS3900 ADD CFMMEP

LST CFMMEP

None None Meaning:Indi-

cates the port

number of the

MEP.

GUI Value

Range:0~5


Range:0~5

Default

Value:None

SingleRAN




107



10 Counters

There are no specific counters associated with this feature.

SingleRAN

Ethernet OAM Feature Parameter Description 10 Counters



108



11 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

SingleRAN

Ethernet OAM Feature Parameter Description 11 Glossary



109



12 Reference Documents

3900 Series Base Station Initial Configuration Guide

SingleRAN

Ethernet OAM Feature Parameter Description 12 Reference Documents