Beruflich Dokumente
Kultur Dokumente
SRAN12.0
Issue 01
Date 2016-09-30
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.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview......................................................................................................................................... 4
2.1 Introduction.................................................................................................................................................................... 4
2.2 Benefits........................................................................................................................................................................... 4
2.3 Architecture.................................................................................................................................................................... 4
6 Related Features...........................................................................................................................20
6.1 GBFD-118630 Ethernet OAM......................................................................................................................................20
6.2 WRFD-050425 Ethernet OAM.................................................................................................................................... 21
6.3 LOFD-003004 Ethernet OAM......................................................................................................................................22
6.4 TDLOFD-003004 Ethernet OAM................................................................................................................................ 23
7 Network Impact........................................................................................................................... 25
7.1 GBFD-118630 Ethernet OAM......................................................................................................................................25
8 Engineering Guidelines............................................................................................................. 27
8.1 When to Use................................................................................................................................................................. 27
8.2 Required Information................................................................................................................................................... 28
8.3 Planning........................................................................................................................................................................ 29
8.3.1 RF Planning............................................................................................................................................................... 29
8.3.2 Network Planning...................................................................................................................................................... 29
8.3.3 Hardware Planning.................................................................................................................................................... 29
8.4 Deployment of Ethernet OAM (IEEE 802.3ah) for GSM............................................................................................29
8.4.1 Requirements............................................................................................................................................................. 29
8.4.2 Data Preparation........................................................................................................................................................ 30
8.4.3 Precautions.................................................................................................................................................................32
8.4.4 Hardware Adjustment................................................................................................................................................32
8.4.5 Activation.................................................................................................................................................................. 32
8.4.6 Activation Observation..............................................................................................................................................33
8.4.7 Reconfiguration......................................................................................................................................................... 34
8.4.8 Deactivation...............................................................................................................................................................34
8.5 Deployment of Ethernet OAM (IEEE 802.3ah) for UMTS......................................................................................... 34
8.5.1 Requirements............................................................................................................................................................. 34
8.5.2 Data Preparation........................................................................................................................................................ 35
8.5.3 Precautions.................................................................................................................................................................36
8.5.4 Hardware Adjustment................................................................................................................................................36
8.5.5 Activation.................................................................................................................................................................. 36
8.5.6 Activation Observation..............................................................................................................................................37
8.5.7 Reconfiguration......................................................................................................................................................... 37
8.5.8 Deactivation...............................................................................................................................................................38
8.6 Deployment of Ethernet OAM (IEEE 802.3ah) for LTE..............................................................................................38
8.6.1 Requirements............................................................................................................................................................. 38
8.6.2 Data Preparation........................................................................................................................................................ 39
8.6.3 Precautions.................................................................................................................................................................39
8.6.4 Hardware Adjustment................................................................................................................................................39
8.6.5 Activation.................................................................................................................................................................. 39
8.6.6 Activation Observation..............................................................................................................................................40
8.6.7 Reconfiguration......................................................................................................................................................... 40
8.6.8 Deactivation...............................................................................................................................................................40
8.7 Deployment of Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731) for GSM.................................... 40
8.7.1 Requirements............................................................................................................................................................. 40
8.7.2 Data Preparation........................................................................................................................................................ 41
8.7.3 Precautions.................................................................................................................................................................47
8.7.4 Hardware Adjustment................................................................................................................................................47
8.7.5 Activation.................................................................................................................................................................. 47
9 Parameters..................................................................................................................................... 67
10 Counters...................................................................................................................................... 89
11 Glossary....................................................................................................................................... 94
12 Reference Documents............................................................................................................... 95
1.1 Scope
This document describes Ethernet Operations, Administration and Maintenance (OAM),
including its technical principles, related features, network impact, and engineering
guidelines.
Ethernet OAM is based on the IEEE 802.3ah, IEEE 802.1ag, and ITU-T Y.1731 protocols.
This document covers the following features:
Table 1-1 lists the Ethernet OAM supported by NEs of each mode.
For definitions of base stations described in this document, see section "Base Station
Products" in SRAN Networking and Evolution Overview Feature Parameter Description.
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier
version
SRAN12.1 01 (2017-03-08)
This issue does not include any changes.
Ethernet OAM Micro base stations do not support Ethernet OAM (which is defined
in ITU-T Y.1731).
2 Overview
2.1 Introduction
With the advent of Internet Protocol (IP) transformation in telecom operator networks,
Ethernet bearer networks are widely used. To guarantee the reliability and availability of
Ethernet services, the Ethernet OAM feature is introduced.
This feature provides detection, notification, verification, and locating functions for detectable
hard faults (such as link disconnection) or undetectable soft faults (such as damages in
memory bridges).
From this version onwards, Ethernet OAM supports three protocols: point-to-point IEEE
802.3ah, end-to-end IEEE 802.1ag, and end-to-end ITU-T Y.1731.
NOTE
Point-to-point Ethernet OAM IEEE 802.3ah: IEEE 802.3ah must be enabled for two pieces of
equipment that are directly connected and Ethernet switch equipment cannot be connected between these
two pieces of equipment.
End-to-end Ethernet OAM IEEE 802.1ag or ITU-T Y.1731: It can be enabled for two pieces of
equipment that are not directly connected, but they must have Layer 2 connectivity provided by Layer 2
switches between them.
2.2 Benefits
The Ethernet OAM feature provides the following benefits:
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.
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.
3.1 Introduction
Ethernet OAM (IEEE 802.3ah) is a point-point Ethernet OAM protocol used to implement the
Ethernet in the First Mile (EFM) OAM function. With this function, the link status is
monitored effectively.
The EFM OAM function must be enabled for two pieces of equipment that are directly
connected during point-point Ethernet OAM services. The function detects faults on Ethernet
links by using the automatic discovery, fault detection, link monitoring, and remote loopback
mechanisms.
After Ethernet OAM (IEEE 802.3ah) is deployed between a base station (or base station
controller) and transmission equipment that is directly connected to the Ethernet interface,
OAM Protocol Data Units (PDUs) are exchanged between the local end and remote end to
detect the link status, as shown in Figure 3-1. However, the remote transmission equipment
must support IEEE 802.3ah.
3.2 Principles
Ethernet OAM (IEEE 802.3ah) supports active and passive modes.
l In active mode, the local end sends negotiation packets to the peer end.
l In passive mode, the local end waits for negotiation packets from the peer end.
It is recommended that Ethernet OAM (IEEE 802.3ah) work in active mode. In applications,
only when both ends at a point-to-point link work in passive mode, neither end initiates the
automatic discovery procedure. The automatic discovery procedure is also known as OAM
discovery. To implement OAM functions, automatic discovery must be enabled first. OAM
clients in different modes have different OAM support capabilities. For details, see Table 3-1.
Figure 3-2 Network topology with Ethernet OAM (IEEE 802.3ah) enabled
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.
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.
Link Monitoring
Link monitoring is used to monitor bit errors, such as errored frames and errored signals on a
link. When the bit error rate (BER) exceeds a specified threshold, the local OAM client
notifies the remote OAM client of the corresponding bit error event by sending an Event
Notification OAM PDU. Then, the remote OAM client reports the link fault to the local OAM
client.
To measure the performance from different perspectives, the link monitoring function is
divided into errored frame event monitoring, errored frame seconds event monitoring, and
errored frame period event monitoring.
l Errored frame event monitoring: The errored frame event monitoring period refers to the
period in which errored frames are measured once. In this period, the number of detected
errored frames is greater than or equal to the specified errored frame event threshold.
The related parameters in GSM, UMTS, and LTE modes are as follows:
NOTE
l The GBTS and eGBTS use different MML commands, and therefore they may use different
parameter IDs and names.
l Unless otherwise specified, "base station controller" in this document is a generic term for
GSM and UMTS modes.
l Errored frame seconds event monitoring: In an errored frame seconds summary event
period, the number of detected errored frame seconds is greater than or equal to the
specified errored frame seconds summary event threshold. An errored frame seconds
event indicates that at least one errored frame is detected in a second. The related
parameters in GSM, UMTS, and LTE modes are as follows:
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.
Remote Loopback
In a remote loopback, the local OAM client sends packets to the remote OAM client, and the
remote OAM client loops back packets other than non-OAM PDUs. The remote loopback
function can be used to locate link faults and check link quality.
The local OAM client sends a Loopback Control OAM PDU to the remote OAM client,
instructing it to enter the loopback state. As shown in Figure 3-4, after the remote OAM
client enters the loopback state, the local OAM client sends packets to the remote OAM client
and then calculates the packet loss rate and other KPIs on the current link based on the
number of the sent and received packets.
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:
4.1 Introduction
The Ethernet OAM (IEEE 802.1ag) is an end-to-end Ethernet OAM protocol used to
implement the Connectivity Fault Management (CFM) function. The CFM function is a
network-level Ethernet OAM technology and comprises continuity check, loopback, and
linktrace functions. With the CFM function, the continuity faults on the entire network can be
detected and located.
If the base station or base station controller detects Ethernet faults or undesirable network
performance using Ethernet OAM (IEEE 802.1ag), it initiates rerouting, port switchover, or
board switchover accordingly, to ensure normal connection of Ethernet links.
4.2 Principles
Ethernet OAM (IEEE 802.1ag) reports the status of the data link layer and therefore
effectively monitors and manages the network. To enable Ethernet OAM (IEEE 802.1ag), the
local end and remote end on the network must support IEEE 802.1ag.
To implement end-to-end Ethernet link maintenance and fault detection and isolation,
Ethernet OAM (IEEE 802.1ag) defines Maintenance Domain (MD), Maintenance Association
(MA), Maintenance Point (MP), Maintenance End Point (MEP), and Maintenance
Intermediate Point (MIP).
Ethernet OAM (IEEE 802.1ag) implements the service-based end-to-end detection. In
addition, it detects the network segments along the same service flow one by one.
l MD
The maintenance domain name is specified by the MDNAME parameter and denotes a
network or a part of a network in which the CFM is implemented. An MD is usually
managed by an Internet Service Provider (ISP) or an operator.
MDs can be managed on a per level basis. The level of an MD is specified by the Level
parameter. A high-level MD can span low-level MDs, but a low-level MD cannot span
high-level MDs. This level-based MD management allows the same service flow to be
maintained segment by segment and also applies to different service flows.
Ethernet OAM (IEEE 802.1ag) supports eight MD levels, ranging from 0 to 7. Level 7 is
the highest MD level, and level 0 is the lowest.
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.
Figure 4-2 Network topology with Ethernet OAM (IEEE 802.1ag) enabled
receiving the Link Trace Message, the destination MEP responds with a Link Trace
Reply message to the local MEP.
– If the destination MEP terminates the Link Trace Message upon receiving it and
returns a Link Trace Reply to the local MEP, the link trace is successful.
– If the local MEP does not receive the Link Trace Reply message from the
destination MEP before the timer specified by the local MEP expires, the link trace
fails.
NOTE
The LT function cannot be enabled for links between the local MEP and MIPs.
In addition, the Link Trace Reply message contains the Time to Live (TTL) parameter
which specifies the position of the MP that responds with the message on the tested link.
LT is similar to TraceRoute and therefore is also called MAC TRACE.
5.1 Introduction
Ethernet OAM (ITU-T Y.1731) is an enhancement of Ethernet OAM (IEEE 802.1ag). In
addition to the CFM function specified by IEEE 802.1ag, Ethernet OAM (ITU-T Y.1731)
implements the Performance Management function. The Performance Management function
allows the base station to perform single-ended Ethernet Loss Measurement (ETH-LM), two-
way Ethernet Delay Measurement (ETH-DM), and delay variation measurement.
Ethernet OAM (TU-T Y.1731) is defined by ITU-T Y.1731 (2008). Ethernet OAM (ITU-T Y.
1731) is supported only on the base station side.
5.2 Principles
The working principle for Ethernet OAM (ITU-T Y.1731) is similar to that for Ethernet OAM
(IEEE 802.1ag). For details, see section 4.2 Principles. The only difference is as follows:
To simplify the implementation, Ethernet OAM (ITU-T Y.1731) incorporates the following
changes:
l Combines MD and MA into a Maintenance Entity Group (MEG).
l Replaces the MA ID with MEG ID.
l Replaces MD level with MEG Level.
The definitions of MEPs, MIPs are the same in Ethernet OAM (ITU-T Y.1731) and Ethernet
OAM (IEEE 802.1ag).
Figure 5-1 Network topology with Ethernet OAM (ITU-T Y.1731) enabled
Each MEP on the base station side can measure the following items:
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.
Upon receiving the LMR message, the base station uses the following values contained in the
message for local- and remote-end loss measurements:
l The respective values of the TxFCf, RxFCf, and TxFCb counters are TxFCf[tc],
RxFCf[tc], and TxFCb[tc] when the base station receives the LMR message. In this
message, the value of the local counter RxFCl is RxFCl[tc].
NOTE
The "tc" in the RxFCl[tc] indicates the time when the base station receives the current LMR message.
l The respective values of the TxFCf, RxFCf, and TxFCb counters are TxFCf[tp],
RxFCf[tp], and TxFCb[tp] when the base station receives the previous LMR message. In
this message, the value of the local counter RxFCl is RxFCl[tp].
NOTE
The "tp" in the RxFCl[tp] indicates the time when the base station receives the previous LMR message.
Based on the preceding values carried in LMR messages, the remote-end frame loss (in the
uplink) is calculated using the following formula:
Remote-end frame loss = (TxFCf[tc] – TxFCf[tp]) – (RxFCf[tc] – RxFCf[tp])
The local-end frame loss (in the downlink) is calculated using the following formula:
Local-end frame loss = (TxFCb[tc] – TxFCb[tp]) – (RxFCl[tc] – RxFCl[tp])
Two-Way ETH-DM
In two-way ETH-DM, if the local MEP sends a DMM frame with the TxTimeStampf value to
the remote MEP, and the remote MEP delays responding with a DMR frame, the delay will be
used as the delay for the entire L2 network. Figure 5-3 shows the detailed message exchanges
between the local MEP and remote MEP. The counters for ETH-DM are described in Table
5-2.
Frame delay = (RxTimeb – TxTimeStampf) – (TxTimeStampb – RxTimeStampf)
The frame delay variation can be calculated using the following formula:
Frame delay variation = Frame delay[tc] – Frame delay[tp]
NOTE
The "tc" indicates the value of the current frame delay, and the "tp" indicates the value of the previous
frame delay on the base station side.
6 Related Features
Ethernet OAM (IEEE 802.1ag) Ethernet OAM (IEEE 802.1ag) is mutually exclusive
with Ethernet OAM (ITU-T Y.1731). This implies that
Ethernet OAM (ITU-T Y.1731) Ethernet OAM (IEEE 802.1ag) and Ethernet OAM
(ITU-T Y.1731) cannot be enabled simultaneously on a
base station.
Impacted Features
Feature ID Feature Name Description
Ethernet OAM (IEEE 802.1ag) Ethernet OAM (IEEE 802.1ag) is mutually exclusive
with Ethernet OAM (ITU-T Y.1731). This implies that
Ethernet OAM (ITU-T Y.1731) Ethernet OAM (IEEE 802.1ag) and Ethernet OAM
(ITU-T Y.1731) cannot be enabled simultaneously on a
base station.
Impacted Features
Feature ID Feature Name Description
Ethernet OAM (IEEE 802.1ag) Ethernet OAM (IEEE 802.1ag) is mutually exclusive
with Ethernet OAM (ITU-T Y.1731). This implies that
Ethernet OAM (ITU-T Y.1731) Ethernet OAM (IEEE 802.1ag) and Ethernet OAM
(ITU-T Y.1731) cannot be enabled simultaneously on a
base station.
Impacted Features
Feature ID Feature Name Description
Ethernet OAM (IEEE 802.1ag) Ethernet OAM (IEEE 802.1ag) is mutually exclusive
with Ethernet OAM (ITU-T Y.1731). This implies that
Ethernet OAM (ITU-T Y.1731) Ethernet OAM (IEEE 802.1ag) and Ethernet OAM
(ITU-T Y.1731) cannot be enabled simultaneously on a
base station.
Impacted Features
Feature ID Feature Name Impact
7 Network 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.
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.
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.
8 Engineering Guidelines
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.
The protocol version supported by the transmission equipment must be the same as that
supported by the radio equipment.
The following table describes the versions for IEEE 802.1ag and ITU-T Y.1731 protocols
supported by the radio equipment.
ITU-T Y.1731 The base station supports ITU-T Y. The base station controller
1731 (2008). does not support ITU-T Y.
1731 (2008).
When deploying Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731), plan the
following data for the base station (or base station controller) and transmission equipment:
8.3 Planning
8.3.1 RF Planning
N/A
8.4.1 Requirements
Hardware
The following boards support Ethernet OAM (IEEE 802.3ah) when they are configured with
Ethernet ports.
NE IEEE 802.3ah
BSC FG2a/FG2c/FG2d/FG2e/GOUa/GOUc/GOUd/EXOUa/
EXOUb
GBTS GTMUb/GTMUc/UTRP2/UTRP9/UTRPc
eGBTS UMPT/GTMUb/GTMUc
Transmission Equipment
License
None
Table 8-1 Data to prepare before activating Ethernet OAM (IEEE 802.3ah) on the BSC side
MO Parameter Name Parameter Setting Data Source
ID Notes
NOTE
Table 8-2 Data to prepare before activating Ethernet OAM (IEEE 802.3ah) on the GBTS side
MO Parameter Parameter ID Setting Data Source
Name Notes
NOTE
8.4.3 Precautions
None
8.4.5 Activation
This section uses the scenario shown in Figure 3-2 as an example to describe how to activate
Ethernet OAM (IEEE802.3ah) using the MML and CME GUI.
NOTE
l To enable Ethernet OAM (IEEE 802.3ah) on the BSC side, you should also enable it on the
transmission equipment.
l To enable Ethernet OAM (IEEE 802.3ah) on the GBTS side, you should also enable it on the
transmission equipment.
8.4.7 Reconfiguration
None
8.4.8 Deactivation
Run the DEA EFMAH command to deactivate Ethernet OAM (IEEE 802.3ah) on a port
configured with EFM OAM.
Run the DEA BTSETHOAMAH command to deactivate Ethernet OAM (IEEE 802.3ah) on
a port configured with EFM OAM.
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.
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 "MML
Command Examples" in section 8.5.8 Deactivation.
8.5.1 Requirements
Hardware
The following boards support Ethernet OAM (IEEE 802.3ah) when they are configured with
Ethernet ports.
NE IEEE 802.3ah
RNC FG2a/FG2c/FG2d/FG2e/GOUa/GOUc/GOUd/EXOUa/
EXOUb
NodeB WMPT/UMPT/UTRP2/UTPR9/UTRPc
Transmission Equipment
License
Table 8-3 Data to prepare before activating Ethernet OAM (IEEE 802.3ah) on the NodeB side
MO Parameter Parameter ID Setting Data Source
Name Notes
8.5.3 Precautions
None
8.5.5 Activation
This section uses the scenario shown in Figure 3-2 as an example to describe how to activate
Ethernet OAM (IEEE802.3ah) using the MML and CME GUI.
NOTE
l To enable Ethernet OAM (IEEE802.3ah) on the RNC side, you should also enable it on the
transmission equipment.
l To enable Ethernet OAM (IEEE802.3ah) on the NodeB side, you should also enable it on the
transmission equipment.
l Work Mode: This parameter specifies the working mode of Ethernet OAM (IEEE
802.3ah).
l Detection Period: This parameter specifies the interval at which a Protocol Data Unit
(PDU) is transmitted for fault detection.
l PDUSIZE: This parameter specifies the length of an OAM PDU packet supported by
Ethernet OAM (IEEE 802.3ah).
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
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.
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.
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
8.6.1 Requirements
Hardware
The following boards support Ethernet OAM (IEEE 802.3ah) when they are configured with
Ethernet ports.
NE IEEE 802.3ah
eNodeB LMPT/UMPT/UTRP2/UTRP9/UTRPc
Transmission Equipment
IEEE 802.3ah The transmission equipment supports Ethernet OAM (IEEE 802.3ah).
License
8.6.3 Precautions
None
8.6.5 Activation
This section uses the scenario shown in Figure 3-2 as an example to describe how to activate
Ethernet OAM (IEEE802.3ah) using the MML and CME GUI.
NOTE
To enable Ethernet OAM (IEEE802.3ah) on the eNodeB side, you should also enable it on the
transmission equipment.
8.6.7 Reconfiguration
None
8.6.8 Deactivation
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.
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.
Transmission Equipment
License
No additional license is required.
Table 8-4 Data to prepare before activating Ethernet OAM (IEEE 802.1ag) or Ethernet OAM
(ITU-T Y.1731) on the BSC side
MO Parameter Parameter ID Setting Notes Data
Name Source
Table 8-5 Data to prepare before activating Ethernet OAM (IEEE 802.1ag) or Ethernet OAM
(ITU-T Y.1731) on the GBTS side
MO Param Parameter ID Setting Notes Data
eter Source
Name
MA MANAME(BSC690 -- Network
Name 0,BSC6910) plan
(negotiation
not required)
8.7.3 Precautions
Ethernet OAM (ITU-T Y.1731) does not support packet loss measurement on an Ethernet
trunk. If packets are calculated for the Ethernet trunk, the performance monitoring data is not
accurate because the sequence of packets is not saved for the Ethernet trunk.
NOTE
To check packet loss statistics for an Ethernet trunk, you can run the DSP ETHTRK command or use
the performance counters in the Measurement of Trunk Performance (TRUNK) function set.
8.7.5 Activation
This section describes how to activate Ethernet OAM (IEEE802.1ag) using the MML
commands and CME GUI, and uses the scenario shown in Figure 4-2 as an example.
NOTE
l To enable Ethernet OAM (IEEE802.1ag) on the base station side, you should also enable it on the
transmission equipment.
l To enable Ethernet OAM (IEEE802.1ag) on the base station controller side, you should also enable
it on the transmission equipment.
Step 1 Run the ADD CFMMD command to add a CFM MD. In this step, set the following
parameters to appropriate values: MDIDX(BSC6900,BSC6910),
LEVEL(BSC6900,BSC6910), and MDNAME(BSC6900,BSC6910).
Step 2 Run the ADD CFMMA command to add an MA. In this step, set the parameters as follows:
Set MDIDX(BSC6900,BSC6910), VLANID(BSC6900,BSC6910),
MAIDX(BSC6900,BSC6910), MANAME(BSC6900,BSC6910) to appropriate values. Set
CCMINTERVAL(BSC6900,BSC6910) to a period of sending CCM packets in the MA.
Step 3 Run the ADD CFMMEP command to add a local MEP. In this step, set MEP Type to
LocalMep(LocalMep).
Step 4 Run the ADD CFMMEP command to add a remote MEP. In this step, set MEP Type to
RemoteMep(RemoteMep).
----End
The preceding steps are used for configuration. The following steps are used for continuity
check and performance management.
l Run the ACT CFMCCMTST command to activate the CC function at a specified local
MEP.
l Run the PING MAC command to start a MAC PING test on the BSC side. During the
implementation of the MAC PING test, ensure that the CC function is enabled at the
local MEP and remote MEP so that the local MEP can obtain the MAC address of the
remote MEP.
l Run the TRC MAC command to start a MAC TRACE test on the BSC side. During the
implementation of the MAC TRACE test, ensure that the CC function is enabled at the
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 Run the SET BTSETHOAM command with Ethernet OAM Type set to
IEEE_802_1AG(IEEE 802.1ag) or ITU_T_Y1731(ITU-T Y.1731). If this parameter is set
to ITU_T_Y1731(ITU-T Y.1731), Monitor Policy must be configured.
Step 2 Run the ADD BTSETHMD command to add a CFM MD.
Step 3 Run the ADD BTSETHMA command to add an MA.
Step 4 Run the ADD BTSETHLCMEP command to add a local MEP.
Step 5 Run the ADD BTSETHRMMEP command to add a remote MEP.
----End
The preceding steps are used for configuration. The following steps are used for continuity
check and performance management.
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
local MEP and remote MEP so that the local MEP can obtain the MAC address of 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 local MEP and remote MEP so that the local MEP can obtain the MAC
address of the remote MEP.
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.
The procedure for activating Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.
1731) using MML commands on the eGBTS side is the same as that on the NodeB side. For
details, see "On the NodeB side" in "Using MML Commands" in section 8.8.5 Activation.
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.
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.
Before using the following method, ensure that the CC function is enabled at the local and
remote ends.
Run the PING BTSCFM or TRC BTSCFM command to start an LB or LT test from the
local MEP to the remote MEP. If the MAC address of the remote MEP is pinged through,
Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.1731) has been activated. If the
MAC address of the remote MEP cannot be pinged through, Ethernet OAM (IEEE 802.1ag)
or Ethernet OAM (ITU-T Y.1731) has not been activated.
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.
8.7.7 Reconfiguration
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):
Step 5 Run the SET BTSETHOAM command with OAM Type set to ITU-T Y.1731.
----End
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 6 Run the SET ETHOAM command with OAM Type set to ITU-T Y.1731.
----End
If you need to change the configuration of Ethernet OAM (ITU-T Y.1731) to the
configuration of Ethernet OAM (IEEE 802.1ag), perform the similar operation.
8.7.8 Deactivation
This feature can be deactivated by deleting all configurations in reverse order.
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).
Step 3 Run the RMV CFMMA command to delete an MA.
----End
On the GBTS side
----End
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.
Transmission Equipment
License
Table 8-6 Data to prepare before activating Ethernet OAM (IEEE 802.1ag) or Ethernet OAM
(ITU-T Y.1731) on the NodeB side
MO Parameter Parameter Setting Notes Data
Name ID Source
8.8.3 Precautions
Ethernet OAM (ITU-T Y.1731) does not support packet loss measurement on an Ethernet
trunk. If packets are calculated for the Ethernet trunk, the performance monitoring data is not
accurate because the sequence of packets is not saved for the Ethernet trunk.
NOTE
To check packet loss statistics for an Ethernet trunk, you can run the DSP ETHTRK command or use
the performance counters in the Measurement of Trunk Performance (TRUNK) function set.
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 commands on the RNC side is the same as that on the BSC side. For
details, see "On the BSC side" in "Using MML Commands" in section 8.7.5 Activation.
On the NodeB side
Step 1 Run the SET ETHOAM command with OAMTYPE set to IEEE_802_1AG(IEEE 802.1ag)
or ITU_T_Y1731(ITU-T Y.1731). If this parameter is set to ITU_T_Y1731(ITU-T Y.1731),
Monitor Policy must be configured.
Step 2 Run the ADD CFMMD command to add a CFM MD.
Step 3 Run the ADD CFMMA command to add a CFM MA.
Step 4 Run the ADD CFMMEP command to add a local MEP.
Step 5 Run the ADD CFMRMEP command to add a remote MEP.
Step 6 Run the ADD CFMBNDIP command to add an RMEP binding IP address. The binding
address can also be used for routes.
----End
The preceding steps are used for configuration. The following steps are used for continuity
check and performance management.
l Run the ACT CFMCC command to activate the CC function at a specified local MEP.
l Run the CFMPING command to start the CFM MAC PING test on the NodeB side.
During the implementation of the MAC PING test, ensure that the CC function is
enabled at the local MEP and remote MEP so that the local MEP can obtain the MAC
address of the remote MEP.
l Run the 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 measurement of bidirectional delay
variation on the local 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.
Before using the preceding methods, ensure that the CC function is enabled at the local and remote
ends.
l In scenarios where the remote MEP and MAC address are known, run the CFMPING or
CFMTRACE. In this command, set Destination Type to MAC(Remote MAC
Address) and enter MAC Address to check the connectivity.
NOTE
8.8.7 Reconfiguration
If the base station supports Ethernet OAM (IEEE 802.1ag)/Ethernet OAM (ITU-T Y.1731)
and you need to need to change the configuration of Ethernet OAM (IEEE 802.1ag) to the
configuration of Ethernet OAM (ITU-T Y.1731) or vice versa, delete the configured MDs,
MAs, MEPs, and RMEPs for Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.
1731) as follows:
The following steps are used to change the configuration of Ethernet OAM (IEEE 802.1ag) to
the configuration of Ethernet OAM (ITU-T Y.1731):
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 6 To change the configuration of Ethernet OAM (IEEE 802.1ag) to the configuration of
Ethernet OAM (ITU-T Y.1731) on the NodeB side, do as follows: run the SET ETHOAM
command with OAMTYPE set to ITU_T_Y1731(ITU-T Y.1731).
----End
8.8.8 Deactivation
Deactivation is to delete all relevant configuration.
The procedure for deactivating Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.
1731) using MML command on the RNC side is the same as that on the BSC side. For details,
see "On the BSC side" in "Using MML Commands" in 8.7.8 Deactivation.
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
The procedure for deactivating Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.
1731) using MML command on the RNC side is the same as that on the BSC side. For details,
see "On the BSC side" in "Using MML Commands" in 8.7.8 Deactivation.
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.
Transmission Equipment
Ethernet OAM (IEEE 802.1ag) The peer transmission equipment supports Ethernet
OAM (IEEE 802.1ag).
Ethernet OAM (ITU-T Y.1731) The peer transmission equipment supports Ethernet
OAM (ITU-T Y.1731).
License
8.9.3 Precautions
Ethernet OAM (ITU-T Y.1731) does not support packet loss measurement on an Ethernet
trunk. If packets are calculated for the Ethernet trunk, the performance monitoring data is not
accurate because the sequence of packets is not saved for the Ethernet trunk.
NOTE
To check packet loss statistics for an Ethernet trunk, you can run the DSP ETHTRK command or use
the performance counters in the Measurement of Trunk Performance (TRUNK) function set.
8.9.5 Activation
8.9.7 Reconfiguration
The reconfiguration procedure on the eNodeB side is the same as that on the NodeB side. For
details, see "On the NodeB side" in section 8.8.7 Reconfiguration.
8.9.8 Deactivation
If ALM-25880 Ethernet Link Fault or ALM-25895 Ethernet Trunk Group Fault is reported
after the CFM CC function is enabled on the Ethernet port or Ethernet trunk group of the base
station and peer NE, clear the alarm with actions recommended for each alarm cause listed in
Table 8-9. The Ethernet trunk group and ALM-25895 Ethernet Trunk Group Fault are
supported by macro base stations only.
Table 8-9 Alarms related to Ethernet OAM (IEEE 802.1ag) or Ethernet OAM (ITU-T Y.
1731)
Alarm Alarm Name Alar
ID m
Seve
rity
25895 Ethernet Trunk Group Fault (supported by macro base stations only) Major
This alarm is reported with either of the following newly added cause
values:
l CCM LOS Fault
l AIS Fault
l RDI Fault
When an Ethernet port in the Ethernet trunk group is faulty, this alarm
is reported without a cause value and alarms with cause values are
masked. If no alarms without a cause value are reported, the alarms
with cause values are reported.
9 Parameters
MDNA BTS390 ADD WRFD- Ethernet Meaning: Indicates the name of the CFM MD.
ME 0, CFMM 050425 OAM GUI Value Range: 1~43 characters
BTS390 D
0 LOFD-0 Ethernet Unit: None
DSP 0300402 OAM(I
WCDM CFMM Actual Value Range: 1~43 characters
A, / EEE
D TDLOF 802.1ag) Default Value: None
BTS390
0 LTE RMV D-00300
CFMM 402 Ethernet
D OAM
GBFD-1
LST 18630
CFMM
D
LEVEL BTS390 ADD WRFD- Ethernet Meaning: Indicates the level of the CFM MD.
0, CFMM 050425 OAM GUI Value Range: 0~7
BTS390 D
0 LOFD-0 Ethernet Unit: None
DSP 0300402 OAM(I
WCDM CFMM Actual Value Range: 0~7
A, / EEE
D TDLOF 802.1ag) Default Value: 0
BTS390
0 LTE DSP D-00300
CFMM 402 Ethernet
A OAM
GBFD-1
DSP 18630
CFMM
EP
DSP
CFMR
MEP
LST
CFMM
D
SRN BSC690 ADD None None Meaning: The subrack number for running this
0 CFMM command
D GUI Value Range: 0~11
RMV Unit: None
CFMM
D Actual Value Range: 0~11
Default Value: None
SRN BSC691 ADD None None Meaning: The subrack number for running this
0 CFMM command
D GUI Value Range: 0~11
RMV Unit: None
CFMM
D Actual Value Range: 0~11
Default Value: None
SN BSC690 ADD None None Meaning: Indicates the slot number for running this
0 CFMM command.
D GUI Value Range: 0~5;8~27
RMV Unit: None
CFMM
D Actual Value Range: 0~5, 8~27
Default Value: None
SN BSC691 ADD None None Meaning: Indicates the slot number for running this
0 CFMM command
D GUI Value Range: 0~27
RMV Unit: None
CFMM
D Actual Value Range: 0~27
Default Value: None
Level BSC690 ADD GBFD-1 Ethernet Meaning: Class of the maintenance domain
0 CFMM 18630 OAM GUI Value Range: 0~7
D
Unit: None
Actual Value Range: 0~7
Default Value: 0
Level BSC691 ADD GBFD-1 Ethernet Meaning: Class of the maintenance domain
0 CFMM 18630 OAM GUI Value Range: 0~7
D
Unit: None
Actual Value Range: 0~7
Default Value: 0
VLANI BSC690 ADD GBFD-1 Ethernet Meaning: Specifies the identifier of a VLAN.
D 0 CFMM 18630 OAM Connectivity Fault Management (CFM) supports the
A creation of a Maintenance Association (MA) on each
VLAN for each Maintenance Domain (MD) Level.
The MA must be in one-to-one mapping with the
VLAN ID.
GUI Value Range: 2~4094
Unit: None
Actual Value Range: 2~4094
Default Value: None
VLANI BSC691 ADD GBFD-1 Ethernet Meaning: Specifies the identifier of a VLAN.
D 0 CFMM 18630 OAM Connectivity Fault Management (CFM) supports the
A creation of a Maintenance Association (MA) on each
VLAN for each Maintenance Domain (MD) Level.
The MA must be in one-to-one mapping with the
VLAN ID.
GUI Value Range: 2~4094
Unit: None
Actual Value Range: 2~4094
Default Value: None
CCMIN BSC690 ADD GBFD-1 Ethernet Meaning: Transmission period of the CCM packet in
TERVA 0 CFMM 18630 OAM the MA
L A GUI Value Range: 10, 100, 1000
Unit: ms
Actual Value Range: 10, 100, 1000
Default Value: 1000
CCMIN BSC691 ADD GBFD-1 Ethernet Meaning: Transmission period of the CCM packet in
TERVA 0 CFMM 18630 OAM the MA
L A GUI Value Range: 10, 100, 1000
Unit: ms
Actual Value Range: 10, 100, 1000
Default Value: 1000
VLANP BSC690 ADD None None Meaning: Priority of the VLAN. The VLAN priority
RI 0 CFMM is used to prioritize packets at the data link layer in an
A Ethernet. 0 indicates the lowest priority. 7 indicates
the highest priority. The high-priority packets are
preferentially transmitted during congestion of links.
GUI Value Range: 0~7
Unit: None
Actual Value Range: 0~7
Default Value: 6
VLANP BSC691 ADD None None Meaning: Priority of the VLAN. The VLAN priority
RI 0 CFMM is used to prioritize packets at the data link layer in an
A Ethernet. 0 indicates the lowest priority. 7 indicates
the highest priority. The high-priority packets are
preferentially transmitted during congestion of links.
GUI Value Range: 0~7
Unit: None
Actual Value Range: 0~7
Default Value: 6
MEPT BSC690 ADD GBFD-1 Ethernet Meaning: The type of the maintenance point added to
YPE 0 CFMM 18630 OAM the maintenance group. LocalMep indicates a local
EP maintenance point and RemoteMep indicates a remote
maintenance point.
GUI Value Range: LocalMep(LocalMep),
RemoteMep(RemoteMep)
Unit: None
Actual Value Range:
LocalMep,
RemoteMep
Default Value: None
MEPT BSC691 ADD GBFD-1 Ethernet Meaning: The type of the maintenance point added to
YPE 0 CFMM 18630 OAM the maintenance group. LocalMep indicates a local
EP maintenance point and RemoteMep indicates a remote
maintenance point.
GUI Value Range: LocalMep(LocalMep),
RemoteMep(RemoteMep)
Unit: None
Actual Value Range:
LocalMep,
RemoteMep
Default Value: None
PORTT BSC690 ADD GBFD-1 Ethernet Meaning: Indicates the type of the physical port .
YPE 0 CFMM 18630 OAM ETHER indicates the ethernet port and TRUNK
EP indicates the aggregation group.
GUI Value Range: ETHER, TRUNK
Unit: None
Actual Value Range: ETHER, TRUNK
Default Value: None
PORTT BSC691 ADD GBFD-1 Ethernet Meaning: Indicates the type of the physical port .
YPE 0 CFMM 18630 OAM ETHER indicates the ethernet port and TRUNK
EP indicates the aggregation group.
GUI Value Range: ETHER, TRUNK
Unit: None
Actual Value Range: ETHER, TRUNK
Default Value: None
OAMT BSC690 SET GBFD-1 Ethernet Meaning: Indicates the type of BTS Ethernet OAM.
YPE 0 BTSET 18630 OAM GUI Value Range: IEEE_802_1AG(IEEE 802.1ag),
HOAM ITU_T_Y1731(ITU-T Y.1731)
Unit: None
Actual Value Range: IEEE_802_1AG, ITU_T_Y173
Default Value: IEEE_802_1AG(IEEE 802.1ag)
OAMT BSC691 SET GBFD-1 Ethernet Meaning: Indicates the type of BTS Ethernet OAM.
YPE 0 BTSET 18630 OAM GUI Value Range: IEEE_802_1AG(IEEE 802.1ag),
HOAM ITU_T_Y1731(ITU-T Y.1731)
Unit: None
Actual Value Range: IEEE_802_1AG, ITU_T_Y173
Default Value: IEEE_802_1AG(IEEE 802.1ag)
MONIT BSC690 SET GBFD-1 Ethernet Meaning: This parameter indicates monitoring policy,
ORPOL 0 BTSET 18630 OAM and is valid only if "OAMTYPE" is set to
ICY HOAM ITU_T_Y1731.
GUI Value Range: PORTID_VLANID(Based on
PortID and VLANID),
PORTID_VLANID_VLANPRI(Based on
PortID,VLANID and VLAN PRI),
SA_DA_VLANID(Based on SA,DA and VLANID),
SA_DA_VLANID_VLANPRI(Based on
SA,DA,VLANID and VLAN PRI), SA_DA(Based on
SA and DA)
Unit: None
Actual Value Range: PORTID_VLANID,
PORTID_VLANID_VLANPRI, SA_DA_VLANID,
SA_DA_VLANID_VLANPRI, SA_DA
Default Value: PORTID_VLANID_VLANPRI(Based
on PortID,VLANID and VLAN PRI)
MONIT BSC691 SET GBFD-1 Ethernet Meaning: This parameter indicates monitoring policy,
ORPOL 0 BTSET 18630 OAM and is valid only if "OAMTYPE" is set to
ICY HOAM ITU_T_Y1731.
GUI Value Range: PORTID_VLANID(Based on
PortID and VLANID),
PORTID_VLANID_VLANPRI(Based on
PortID,VLANID and VLAN PRI),
SA_DA_VLANID(Based on SA,DA and VLANID),
SA_DA_VLANID_VLANPRI(Based on
SA,DA,VLANID and VLAN PRI), SA_DA(Based on
SA and DA)
Unit: None
Actual Value Range: PORTID_VLANID,
PORTID_VLANID_VLANPRI, SA_DA_VLANID,
SA_DA_VLANID_VLANPRI, SA_DA
Default Value: PORTID_VLANID_VLANPRI(Based
on PortID,VLANID and VLAN PRI)
MDNA BSC690 ADD GBFD-1 Ethernet Meaning: Name of the maintenance domain.
ME 0 BTSET 18630 OAM GUI Value Range: 1~20 characters
HMD
Unit: None
RMV
BTSET Actual Value Range: 1~20 characters
HMD Default Value: None
MDNA BSC691 ADD GBFD-1 Ethernet Meaning: Name of the maintenance domain.
ME 0 BTSET 18630 OAM GUI Value Range: 1~20 characters
HMD
Unit: None
RMV
BTSET Actual Value Range: 1~20 characters
HMD Default Value: None
MDLE BSC690 ADD GBFD-1 Ethernet Meaning: Level of the maintenance domain.The
VEL 0 BTSET 18630 OAM priority of the maintenance domain ranks from 0 to 7
HMD from low to high.
GUI Value Range: 0~7
Unit: None
Actual Value Range: 0~7
Default Value: 0
MDLE BSC691 ADD GBFD-1 Ethernet Meaning: Level of the maintenance domain.The
VEL 0 BTSET 18630 OAM priority of the maintenance domain ranks from 0 to 7
HMD from low to high.
GUI Value Range: 0~7
Unit: None
Actual Value Range: 0~7
Default Value: 0
MDNA BSC690 ADD GBFD-1 Ethernet Meaning: Name of the maintenance domain.
ME 0 BTSET 18630 OAM GUI Value Range: 1~20 characters
HMA
Unit: None
RMV
BTSET Actual Value Range: 1~20 characters
HMA Default Value: None
MDNA BSC691 ADD GBFD-1 Ethernet Meaning: Name of the maintenance domain.
ME 0 BTSET 18630 OAM GUI Value Range: 1~20 characters
HMA
Unit: None
RMV
BTSET Actual Value Range: 1~20 characters
HMA Default Value: None
MANA BSC690 ADD GBFD-1 Ethernet Meaning: Name of the maintenance association.
ME 0 BTSET 18630 OAM GUI Value Range: 1~20 characters
HMA
Unit: None
RMV
BTSET Actual Value Range: 1~20 characters
HMA Default Value: None
MANA BSC691 ADD GBFD-1 Ethernet Meaning: Name of the maintenance association.
ME 0 BTSET 18630 OAM GUI Value Range: 1~20 characters
HMA
Unit: None
RMV
BTSET Actual Value Range: 1~20 characters
HMA Default Value: None
VLANI BSC690 ADD GBFD-1 Ethernet Meaning: VLAN ID of the service type.
D 0 BTSET 18630 OAM GUI Value Range: 1~4094
HMA
Unit: None
Actual Value Range: 1~4094
Default Value: 1
VLANI BSC691 ADD GBFD-1 Ethernet Meaning: VLAN ID of the service type.
D 0 BTSET 18630 OAM GUI Value Range: 1~4094
HMA
Unit: None
Actual Value Range: 1~4094
Default Value: 1
MDNA BSC690 ADD GBFD-1 Ethernet Meaning: Name of the maintenance domain.
ME 0 BTSET 18630 OAM GUI Value Range: 1~20 characters
HLCM
EP Unit: None
MDNA BSC691 ADD GBFD-1 Ethernet Meaning: Name of the maintenance domain.
ME 0 BTSET 18630 OAM GUI Value Range: 1~20 characters
HLCM
EP Unit: None
MANA BSC690 ADD GBFD-1 Ethernet Meaning: Name of the maintenance association.
ME 0 BTSET 18630 OAM GUI Value Range: 1~20 characters
HLCM
EP Unit: None
MANA BSC691 ADD GBFD-1 Ethernet Meaning: Name of the maintenance association.
ME 0 BTSET 18630 OAM GUI Value Range: 1~20 characters
HLCM
EP Unit: None
MEPID BSC690 ADD GBFD-1 Ethernet Meaning: Identifies a maintenance end point (MEP) of
0 BTSET 18630 OAM a maintenance association.
HLCM GUI Value Range: 1~8191
EP
Unit: None
RMV
BTSET Actual Value Range: 1~8191
HLCM Default Value: None
EP
MEPID BSC691 ADD GBFD-1 Ethernet Meaning: Identifies a maintenance end point (MEP) of
0 BTSET 18630 OAM a maintenance association.
HLCM GUI Value Range: 1~8191
EP
Unit: None
RMV
BTSET Actual Value Range: 1~8191
HLCM Default Value: None
EP
MDNA BSC690 ADD GBFD-1 Ethernet Meaning: Name of the maintenance domain.
ME 0 BTSET 18630 OAM GUI Value Range: 1~20 characters
HRMM
EP Unit: None
MDNA BSC691 ADD GBFD-1 Ethernet Meaning: Name of the maintenance domain.
ME 0 BTSET 18630 OAM GUI Value Range: 1~20 characters
HRMM
EP Unit: None
MANA BSC690 ADD GBFD-1 Ethernet Meaning: Name of the maintenance association.
ME 0 BTSET 18630 OAM GUI Value Range: 1~20 characters
HRMM
EP Unit: None
MANA BSC691 ADD GBFD-1 Ethernet Meaning: Name of the maintenance association.
ME 0 BTSET 18630 OAM GUI Value Range: 1~20 characters
HRMM
EP Unit: None
MEPID BSC690 ADD GBFD-1 Ethernet Meaning: Identifies a maintenance end point (MEP) of
0 BTSET 18630 OAM a maintenance association.
HRMM GUI Value Range: 1~8191
EP
Unit: None
RMV
BTSET Actual Value Range: 1~8191
HRMM Default Value: None
EP
MEPID BSC691 ADD GBFD-1 Ethernet Meaning: Identifies a maintenance end point (MEP) of
0 BTSET 18630 OAM a maintenance association.
HRMM GUI Value Range: 1~8191
EP
Unit: None
RMV
BTSET Actual Value Range: 1~8191
HRMM Default Value: None
EP
OAMT BTS390 SET LOFD-0 Ethernet Meaning: Indicates the type of Ethernet OAM. The
YPE 0, ETHO 0300402 OAM current Ethernet OAM type includes IEEE 802.1ag or
BTS390 AM / (IEEE ITU-T Y.1731 ETHOAM.
0 LST TDLOF 802.1ag) GUI Value Range: IEEE_802_1AG(IEEE 802.1ag),
WCDM ETHO D-00300 Ethernet ITU_T_Y1731(ITU-T Y.1731)
A, AM 402 OAM
BTS390 Unit: None
LOFD-0 (Y.1731)
0 LTE 0300403 Actual Value Range: IEEE_802_1AG, ITU_T_Y1731
/ Ethernet Default Value: IEEE_802_1AG(IEEE 802.1ag)
TDLOF OAM
D-00300
403
GBFD-1
18630
MONIT BTS390 SET LOFD-0 Ethernet Meaning: Indicates the ITU-T Y.1731 monitoring
ORPOL 0, ETHO 0300403 OAM policy. The monitoring policy includes the following
ICY BTS390 AM / (Y.1731) values: PORTID_VLANID (based on PortID and
0 LST TDLOF VLANID), PORTID_VLANID_VLANPRI (based on
WCDM D-00300 Ethernet PortID, VLANID, and VLAN PRI),
ETHO OAM
A, AM 403 SA_DA_VLANID (based on PortID, source MAC
BTS390 address, destination MAC address, and VLANID),
0 LTE GBFD-1 SA_DA_VLANID_VLANPRI (based on PortID,
18630 source MAC address, destination MAC address,
VLANID, and VLAN PRI), and SA_DA (based on
PortID, source MAC address, and destination MAC
address).
GUI Value Range: PORTID_VLANID(Based on
PortID and VLANID),
PORTID_VLANID_VLANPRI(Based on
PortID,VLANID and VLAN PRI),
SA_DA_VLANID(Based on SA,DA and VLANID),
SA_DA_VLANID_VLANPRI(Based on
SA,DA,VLANID and VLAN PRI), SA_DA(Based on
SA and DA)
Unit: None
Actual Value Range: PORTID_VLANID,
PORTID_VLANID_VLANPRI, SA_DA_VLANID,
SA_DA_VLANID_VLANPRI, SA_DA
Default Value: PORTID_VLANID_VLANPRI(Based
on PortID,VLANID and VLAN PRI)
MDNA BTS390 ADD WRFD- Ethernet Meaning: Indicates the name of the MD to which the
ME 0, CFMM 050425 OAM MA belongs.
BTS390 A GUI Value Range: 1~43 characters
0 LOFD-0 Ethernet
DSP 0300402 OAM(I Unit: None
WCDM CFMM
A, / EEE Actual Value Range: 1~43 characters
A TDLOF 802.1ag)
BTS390 Default Value: None
0 LTE MOD D-00300
CFMM 402 Ethernet
A OAM
GBFD-1
RMV 18630
CFMM
A
LST
CFMM
A
MANA BTS390 ADD WRFD- Ethernet Meaning: Indicates the name of the MA.
ME 0, CFMM 050425 OAM GUI Value Range: 1~43 characters
BTS390 A
0 LOFD-0 Ethernet Unit: None
DSP 0300402 OAM(I
WCDM CFMM Actual Value Range: 1~43 characters
A, / EEE
A TDLOF 802.1ag) Default Value: None
BTS390
0 LTE MOD D-00300
CFMM 402 Ethernet
A OAM
GBFD-1
RMV 18630
CFMM
A
LST
CFMM
A
BNDVL BTS390 ADD WRFD- Ethernet Meaning: Indicates whether the MA is associated with
AN 0, CFMM 050425 OAM the VLAN.
BTS390 A GUI Value Range: NO(No), YES(Yes)
0 LOFD-0 Ethernet
DSP 0300402 OAM(I Unit: None
WCDM CFMM
A, / EEE Actual Value Range: NO, YES
A TDLOF 802.1ag)
BTS390 Default Value: YES(Yes)
0 LTE LST D-00300
CFMM 402 Ethernet
A OAM
GBFD-1
18630
VLANI BTS390 ADD WRFD- Ethernet Meaning: Indicates the ID of the VLAN with which
D 0, CFMM 050425 OAM the MA is associated.
BTS390 A GUI Value Range: 1~4094
0 LOFD-0 Ethernet
DSP 0300402 OAM(I Unit: None
WCDM CFMM
A, / EEE Actual Value Range: 1~4094
A TDLOF 802.1ag)
BTS390 Default Value: 1
0 LTE LST D-00300
CFMM 402 Ethernet
A OAM
GBFD-1
18630
VLANP BTS390 ADD WRFD- Ethernet Meaning: Indicates the priority of the VLAN with
RI 0, CFMM 050425 OAM which the MA is associated.
BTS390 A GUI Value Range: 0~7
0 LOFD-0 Ethernet
MOD 0300402 OAM(I Unit: None
WCDM CFMM
A, / EEE Actual Value Range: 0~7
A TDLOF 802.1ag)
BTS390 Default Value: 0
0 LTE DSP D-00300
CFMM 402 Ethernet
A OAM
GBFD-1
LST 18630
CFMM
A
MDNA BTS390 ACT WRFD- Ethernet Meaning: Indicates the name of the MD to which the
ME 0, CFMC 050425 OAM MEP belongs.
BTS390 C GUI Value Range: 1~43 characters
0 LOFD-0 Ethernet
ADD 0300402 OAM(I Unit: None
WCDM CFMM
A, / EEE Actual Value Range: 1~43 characters
EP TDLOF 802.1ag)
BTS390 Default Value: None
0 LTE DEA D-00300
CFMC 402 Ethernet
C OAM
GBFD-1
DSP 18630
CFMM
EP
RMV
CFMM
EP
LST
CFMM
EP
MANA BTS390 ACT WRFD- Ethernet Meaning: Indicates the name of the MA to which the
ME 0, CFMC 050425 OAM MEP belongs.
BTS390 C GUI Value Range: 1~43 characters
0 LOFD-0 Ethernet
ADD 0300402 OAM(I Unit: None
WCDM CFMM
A, / EEE Actual Value Range: 1~43 characters
EP TDLOF 802.1ag)
BTS390 Default Value: None
0 LTE DEA D-00300
CFMC 402 Ethernet
C OAM
GBFD-1
DSP 18630
CFMM
EP
RMV
CFMM
EP
LST
CFMM
EP
MEPID BTS390 ACT WRFD- Ethernet Meaning: Indicates the MEP ID.
0, CFMC 050425 OAM GUI Value Range: 1~8191
BTS390 C
0 LOFD-0 Ethernet Unit: None
ADD 0300402 OAM(I
WCDM CFMM Actual Value Range: 1~8191
A, / EEE
EP TDLOF 802.1ag) Default Value: None
BTS390
0 LTE DEA D-00300
CFMC 402 Ethernet
C OAM
GBFD-1
DSP 18630
CFMM
EP
RMV
CFMM
EP
LST
CFMM
EP
MDNA BTS390 ADD WRFD- Ethernet Meaning: Indicates the name of the MD to which the
ME 0, CFMR 050425 OAM RMEP belongs.
BTS390 MEP GUI Value Range: 1~43 characters
0 LOFD-0 Ethernet
DSP 0300402 OAM(I Unit: None
WCDM CFMR
A, / EEE Actual Value Range: 1~43 characters
MEP TDLOF 802.1ag)
BTS390 Default Value: None
0 LTE RMV D-00300
CFMR 402 Ethernet
MEP OAM
GBFD-1
LST 18630
CFMR
MEP
MANA BTS390 ADD WRFD- Ethernet Meaning: Indicates the name of the MA to which the
ME 0, CFMR 050425 OAM RMEP belongs.
BTS390 MEP GUI Value Range: 1~43 characters
0 LOFD-0 Ethernet
DSP 0300402 OAM(I Unit: None
WCDM CFMR
A, / EEE Actual Value Range: 1~43 characters
MEP TDLOF 802.1ag)
BTS390 Default Value: None
0 LTE RMV D-00300
CFMR 402 Ethernet
MEP OAM
GBFD-1
LST 18630
CFMR
MEP
RMEPI BTS390 ADD WRFD- Ethernet Meaning: Indicates the RMEP ID.
D 0, CFMR 050425 OAM GUI Value Range: 1~8191
BTS390 MEP
0 LOFD-0 Ethernet Unit: None
DSP 0300402 OAM(I
WCDM CFMR Actual Value Range: 1~8191
A, / EEE
MEP TDLOF 802.1ag) Default Value: None
BTS390
0 LTE RMV D-00300
CFMR 402 Ethernet
MEP OAM
GBFD-1
LST 18630
CFMR
MEP
MAC BTS390 ADD WRFD- Ethernet Meaning: Indicates the MAC address of the RMEP. It
0, CFMR 050425 OAM must be a valid unicast address in the format of
BTS390 MEP XXXX-XXXX-XXXX. The MAC address of the
0 LOFD-0 Ethernet RMEP can be obtained from the MAC address field
DSP 0300402 OAM(I
WCDM CFMR carried in the CCM message. If the MAC address
A, / EEE configured by the user is different from that carried in
MEP TDLOF 802.1ag)
BTS390 the CCM message, the MAC address carried in the
0 LTE LST D-00300 MAC message prevails.
CFMR 402 Ethernet
MEP OAM GUI Value Range: 14 characters
GBFD-1 Unit: None
18630
Actual Value Range: 14 characters
Default Value: 0000-0000-0000
MDNA BTS390 ADD WRFD- Ethernet Meaning: Indicates the name of the MD to which the
ME 0, CFMB 050425 OAM RMEP belongs.
BTS390 NDIP GUI Value Range: 1~43 characters
0 LOFD-0 Ethernet
RMV 0300402 OAM(I Unit: None
WCDM CFMB
A, / EEE Actual Value Range: 1~43 characters
NDIP TDLOF 802.1ag)
BTS390 Default Value: None
0 LTE LST D-00300
CFMB 402 Ethernet
NDIP OAM
GBFD-1
18630
MANA BTS390 ADD WRFD- Ethernet Meaning: Indicates the name of the MA to which the
ME 0, CFMB 050425 OAM RMEP belongs.
BTS390 NDIP GUI Value Range: 1~43 characters
0 LOFD-0 Ethernet
RMV 0300402 OAM(I Unit: None
WCDM CFMB
A, / EEE Actual Value Range: 1~43 characters
NDIP TDLOF 802.1ag)
BTS390 Default Value: None
0 LTE LST D-00300
CFMB 402 Ethernet
NDIP OAM
GBFD-1
18630
RMEPI BTS390 ADD WRFD- Ethernet Meaning: Indicates the RMEP ID.
D 0, CFMB 050425 OAM GUI Value Range: 1~8191
BTS390 NDIP
0 LOFD-0 Ethernet Unit: None
RMV 0300402 OAM(I
WCDM CFMB Actual Value Range: 1~8191
A, / EEE
NDIP TDLOF 802.1ag) Default Value: None
BTS390
0 LTE LST D-00300
CFMB 402 Ethernet
NDIP OAM
GBFD-1
18630
BNDIP BTS390 ADD WRFD- Ethernet Meaning: Indicates the IP address of the Ethernet port
0, CFMB 050425 OAM or Ethernet trunk corresponding to an RMEP. The
BTS390 NDIP binding IP address must be different from the existing
0 LOFD-0 Ethernet local IP address or the IP address of any effective port
RMV 0300402 OAM(I
WCDM CFMB (including the physical port and loopback port). The
A, / EEE binding IP address must be different from the local IP
NDIP TDLOF 802.1ag)
BTS390 address dynamically negotiated on the PPP or MLPPP
0 LTE LST D-00300 link. During the binding of an IP address, an error
CFMB 402 Ethernet
OAM messaged indicating IP address conflicts may be
NDIP displayed. In this case, list the existing IP address in
GBFD-1
18630 the system that conflicts with the IP address to be
bound by running the related MML commands. Then,
manually resolve the IP address conflicts. To list the
device IP address, run the LST DEVIP or DSP DEVIP
command. To list the local IP address of the remote
maintenance channel, run the LST OMCH or DSP
OMCH command. To list the local IP address of the
PPP link, run the LST PPPLNK or DSP PPPLNK
command. To list the local IP address of the MLPPP
group, run the LST MPGRP or DSP MPGRP
command. To list the IP address of the local
maintenance channel, run the LST LOCALIP or DSP
LOCALIP command.
GUI Value Range: Valid IP address
Unit: None
Actual Value Range: Valid IP address
Default Value: None
10 Counters
11 Glossary
12 Reference Documents
None