04-OptiX RTN Equipment ETH-OAM Feature-20100331-A

www.huawei.
com
Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.
ETH-OAM Feature of
the OptiX RTN
Equipment

RTN Product Team of Network
Product Service Dept
Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved. Page
Introduction
This course is prepared on the basis of the
introduction and application of hybrid microwave
products.
With the continuous development of the Ethernet,
carriers focus more than ever on the equipment
maintainability. Solutions to OAM of the
transmission network are required urgently. Thus,
the ETH-OAM is developed. This course is
intended to help field engineers understand the
ETH-OAM function of RTN Hybrid microwave
products and master the principle and usage of
the ETH-OAM.
Guidelines for Learning
This course describes the ETH-
OAM function of the RTN hybrid
microwave.
For details, see the descriptions
of the ETH-OAM in the RTN
product feature description.
Objectives
After learning this course, you will be
familiar with:
Principle of the ETH-OAM
Usage of the ETH-OAM
Contents
Introduction
End-to-End 802.1ag OAM
Point-to-Point 802.3ah OAM
Ethernet Service OAM (802.1ag, 802.3ah)
Background
Networks are evolving to IP-based networks.
Ethernet services do not support powerful operation,
management, and maintenance capabilities as SDH
services. No effective fault locating methods or tools
are available if a service link becomes faulty.
Point-to-point Ethernet links between two directly-
connected devices (in the first mile) raise
requirements for detecting a link fault or monitoring
performance.
A
6
0
5
D
CORE
Access Access
ME
ME
B C
IEEE 802.1ag
IEEE 802.3ah IEEE 802.3ah
IEEE 802.1ag: (1) Continuity check (CC): This
method can check the link status in real time
and is used to check unidirectional continuity.
(2) Loopback (LB): This method can locate or
detect a fault at one end. LB is used to check
bidirectional connectivity. (3) Link trace (LT):
This method is used to locate a fault on site.
IEEE 802.3ah: This method focuses on
performance monitoring and fault locating for
the physical links in the first mile.
RNC
Description of scenarios
Application of the 802.3ah OAM and the
802.1ag OAM in the Network
The IEEE 802.1ag OAM focuses on the maintenance of end-to-end Ethernet
links. Its application is based on services.
The IEEE 802.3ah OAM focuses on the maintenance of point-to-point
Ethernet links between two directly-connected devices in the first mile. Its
application is not specific to services.
Contents
Introduction
Contents
Overview
Basic Concepts
Basic Functions
CC
LB
LT
OAM Ping
Overview of the IEEE 802.1ag OAM
Implements the OAM of end-to-end Ethernet links (which can
cross multiple bridge nodes).
Based on services, realizes end-to-end detection in the unit of
"maintenance domain".
Differentiates the VLAN OAMs.
Major functions:
CC
LB
LT
OAM Ping
Data Units of the IEEE 802.1ag
OAM Mac Destination Address: indicates the MAC address of the sink MP.OAM
Mac Source Address: Indicates the MAC address of the source MP.
Ether Type(VLAN): indicates the type of Ethernet data, such as 0x8100.
VLAN tag: indicates the VLAN value of the service traffic.
Ether Type(OAM): The type of the IEEE 802.1ag OAM packet is 0x8809.
OAM Type: specifies how an MP differs and responds to various OAM
operations according to the types of OAM packets.
Basic Concepts of the IEEE 802.1ag OAMMD
Maintenance Domain (MD)
An MD indicates a network that requires the OAM. Multiple
MAs can be configured under an MD.
Attributes of an MD:
MD Name: uniquely identifies an MD. Therefore, MD names in one
network cannot be the same.
Level (optional. The default value is 0. The greater the value is, the
higher the level is.)
Basic Concepts of the IEEE 802.1ag OAMMA
Maintenance Association (MA)
The MA is used to detect the internal continuity of the MD. An MA is a
part of an MD. An MD can be divided into one MA or multiple MAs. An
MA name must be unique in one MD. MA names in different MDs can
be the same. On the network of a carrier, a VLAN is corresponding to a
service instance. On the equipment, a VLAN is corresponding to an MA
or multiple MAs. By classifying MAs, you can detect the connectivity
faults of a network that transmits a certain service instance.
The CCM interval can be configured inside an MA to specify the CCM
sending frequency of all the MEPs inside the MA. The CCM sending
frequency of all the MEPs inside one MA must be the same.
Attributes of an MA:
MA Name
QinQ CCM Interval
An MA inherits all attributes of the corresponding MD.
Basic Concepts of the IEEE 802.1ag OAMMP
A maintenance point (MP) is a functional entity of the IEEE 802.1ag OAM. It
consists of one or more maintenance end points (MEPs) and maintenance
intermediate point (MIPs). Each MP has a maintenance point identification
(MPID). This ID is unique in the entire maintenance association (MA). The
information about the MP is recorded in the MAC address table, MP table,
and routing table. The service type, service ID, and VLAN tag are key
contents in the MP configuration information. Once the MP is created
successfully, the protocol packet carrying the information about this MP is
broadcast to other MPs that are associated with services. Then, these MPs
receive the protocol packet and record the information for future use. The
MEP initiates all the OAM operations and the MIP does not initiate
any OAM operation or send any OAM packet.
Basic Concepts of the IEEE 802.1ag OAMMEP/MIP
MPs are classified into the MEP and MIP:
MEP
It defines the start position of an MA. MEPs are the
originating and terminating points of OAM packets. MEPs
are directional and related to services. All OAM operations
and OAM packets are initiated by MEPs.
MIP
The MIP cannot initiate an OAM packet. The MIP can
respond to and forward an LB or LT packet, and can only
forward a CC packet.
Logical Relationship Inside an MD
Hierarchy: customer ME > service provider ME > operator ME.
The dashed lines in the diagram show the logic channels where IEEE 802.1ag OAM packets pass
through. The MPs at different levels process the OAM protocol packets as follows: In the case of
the OAM protocol packets whose level is higher, the maintenance points transparently transmit
them. In the case of the OAM protocol packets whose layer level is lower, the MPs discard them
directly. In the case of the OAM protocol packets whose level is the same, the maintenance points
respond to or end the packets according to the messages types of the OAM protocol packets.
Contents
Overview
Basic Concepts
Basic Functions
CC
LB
LT
OAM Ping
CORE Access
Access
MEPA
Basic Functions of the IEEE 802.1ag OAMCC
Is the link from
MEP A to MEP B
in normal state?
MEPB
Count CC
packets.
CC_LOC
Alarm!
Requirements of the scenario:
(1) Ethernet services are configured between devices.
(2) The link status is checked in real time.
RNC
CC
As shown in the figure, after the CC is activated, MEPA sends a CCM according to the Ethernet service
trail. After identifying the first CCM, MEPB in the same MD starts a timer for reception of the CCMs from
MEPA. If the link is faulty and the MEPB does not receive the CCM within the period 3.5 times the
timeout duration, MEPB reports the ETH_CFM_LOC alarm until the link recovers to normal.
The frequency of sending CCMs can be 1s, 10s, 1 min, or 10 min.
CORE Access
Access
RNC
MEPA
Basic Functions of the IEEE 802.1ag OAMLB
Is the link from
MEP A to MEP B
in normal state?
MEPB
LBM
LBR
Successful
LB
Does the loopback
return (LBR) from
MEP B time out?
LBM
Failed LB
(2)The fault is located by performing loopbacks point by point.
A loopback test is based on bidirectional services. The source MEP constructs a Loopback Message
(LBM) packet, fills the ID of the sink MP (MIP or MEP), transmits the packet, and starts the timer.
After receiving the LBM packets, the sink MP constructs the LBR packets and transmits them back to the
source MEP. In this case, the loopback test is successful. If the source MEP timer times out and fails to
receive the LBR from the sink MP, the loopback test fails. As shown in the figure, MEPA sends LBM
packets to the sink MEPB. After receiving the packets, MIPC and MIPD in the same MD find that the
sink MPID in the packets are different from their MPIDs, and thus transmit the packets transparently.
After receiving the packets, the sink MEP4 transmits the LBR packets back to the source MEP1. At this
moment, the loopback test is complete. Only MEPs can initiate loopback tests, and MEPs and MIPs can
serve as the receiving end of the detection.
MIPC
MIPD
Basic Functions of the IEEE 802.1ag OAMLT
Application Scenario
(2) The fault is located at one time.
A
605D
CORE
Access Access
LTM
ME
ME
LTR
The LTM cannot
reach D because of
a link failure
between C and D.
A does not receive the
LTR and A reports the
unavailability to D.
B C
Node B: normal
LTM
LTR
Node C: normal
Node D: faulty
LTM
RNC
The source MEP constructs a Link Trace Message (LTM) packet, fills the D of the sink MEP in the packet,
transmits the packet, and starts the timer. All MIPs on the link in the same MD continue to transmit the
received LTM packet to the sink MEP and return an LTR packet to the source MEP. After the sink MEP
receives the LTM packets, the packet transmission is complete. Then, the sink MEP transmits LTR packets
back to the sink. In this case, the link trace test is successful. If the source MEP fails to receive the LTR
packet from the sink MEP until its timer expires, the LT test fails.
Basic Functions of the IEEE 802.1ag OAM
OAM Ping
OAM ping test:
MPID-Ping: When the Ethernet service processing boards of the
Huawei equipment at both ends support the IEEE 802.1ag OAM, the
MP on the Ethernet service processing board at one end initiates
ping tests to the MP on the Ethernet service processing board at the
other end. When the equipment at both ends supports the ARP and
ICMP protocols, only Huawei equipment can initiate a ping test and
Huawei equipment does not respond to a request for a ping test from
the opposite equipment.
Contents
Introduction
Contents
Overview
Basic Concepts
Basic Functions
Auto-discovery
Link performance monitoring
Remote fault detection
Remote loopback
Self-loop check
Overview of the IEEE 802.3ah OAM
The IEEE 802.3ah OAM focuses on the maintenance of
Ethernet physical links between two devices in the last mile.
Major functions:
Auto-discovery
Remote fault detection
Remote loopback
Self-loop check
The IEEE 802.3ah OAM does not implement the functions
irrelevant to a single link, for example, node position
management, protection switching, and bandwidth
reservation and allocation.
Overview of the IEEE 802.3ah OAM
The MAC destination address of an 802.3ah protocol packet
is a fixed multicast address.
The IEEE 802.3ah protocol is a slow protocol. The packet
sending frequency is 1s.
The 802.3ah protocol packets cannot be forwarded by the
network bridge. No matter whether the IEEE 802.3ah OAM
function is available or is activated, 802.3ah protocol
packets cannot be forwarded across hops.
The IEEE 802.3ah protocol specifies that 802.3ah
handshake packets are sent between the equipment at both
ends to keep the handshake state.
Ethernet Port OAMIEEE 802.3ah OAM
Microwave/Optical ring
RNC
2
When a fault at the local end is detected, the remote equipment
can be notified.
1
When the bit error performance (error frame or error signal) is
detected on the receive link at the local end, the remote
equipment can be notified.
3
A fault can be located.

Values and Features
4
The loopback on the port and the intra-board loopback can be
detected.
Error frames or
bit errors are
detected./
A fault on the
local segment
is detected.
Initiate
Loopback
at Local
Respond
to a
loopback.
Check the alarms that are
reported when a loopback is
performed on the port.
(1) The status of the physical link is
checked.
Description of scenarios:
(1) The service performance of
the link is monitored in real
time.
(2) The fault at the remote end
is monitored in real time.
(3)The fault is located on site.
(4)The self-loop is detected.
802.3ah Protocol Data Unit (OAMPDU)
Indicates the slow protocol multicast address. It is fixed as 0x01-80-
C2-00-00-02.
Indicates the MAC address of a port.
Indicates the data part of an OAM PDU.
Indicates the slow protocol type. It is always set to 0x8809.
Is always set to 0x03, indicating the IEEE 802.3ah OAM subtype.
Indicates the status information, such as link fault, critical fault, and
emergency event.
Identifies IEEE 802.3ah OAM protocol packets of different types.
Indicates the frame check sequence.
Basic Concepts of the IEEE 802.3ah
OAMOAM Mode
OAM Mode
Active: Link discovery and remote loopback can be initiated
actively in this mode.
Passive: Link discovery and remote loopback cannot be
initiated actively in passive mode. Other processing
methods are the same as those in active mode.

Basic Functions of the IEEE 802.3ah
OAMAuto-Discovery
Active
Passive
NE1 NE2
NE1 initiates discovery
actively and transmits a
packet carrying its OAM
information.
After receiving a packet from NE1,
NE2 checks whether the setting in
the packet is consistent with the
local setting, and then sends an
OAM packet that carries the
settings of NE1 and NE2.
After receiving an OAM packet from
NE2, NE1 updates the setting of NE2
at the local end, and checks whether
the settings are consistent. After that,
the OAM packets transmitted by NE1
carry the settings of NE1 and NE2.
802.3ah packet sent by NE1
802.3ah packet sent by NE2
By exchanging the information OAM protocol data unit (OAMPDU)
periodically, the equipment at local end is informed whether the
opposite end supports the IEEE 802.3ah OAM protocol. OAM auto-
discovery is a prerequisite to realizing the link performance monitoring
and remote loopback. The discovery procedure can be initiated by only
the active end. The equipment at both ends can be in active mode at
the same time, or one is in active mode and the other is in passive
mode. The equipment at both ends cannot be in passive mode at the
same time.
The packet sending frequency is 1s during the discovery procedure.
The contents to be negotiated during the discovery procedure include
whether the remote loopback is supported, whether the error frame
detection and bit error detection are supported, and whether the fast
test (not specified by the protocol) is supported. The discovery
procedure ends only after the contents at both ends are negotiated
successfully.
The handshake procedure starts immediately after the discovery
procedure.
IEEE 802.3ah OAM Handshake Phase
In the handshake phase, handshake packets are continuously
sent at a frequency of 1s.
All 3AH packets including normal handshake packets, fault
notification packets, and loopback packets can be kept in
handshake state.
If no 3AH packet is received within 5s, it is considered that the link
is faulty and the process goes back to the discovery phase.
If the negotiation fails due to the configuration modification at
either end during the handshake phase, the process goes back to
the discovery phase.
OAMLink Performance Monitoring
The link performance monitoring method monitors the bit error performance (error
frames or error signals) of a link. On detecting that bit errors exceed the threshold,
the local end sends the specific bit error event to the opposite end through the event
notification OAMPDU. In this case, the opposite end reports the alarm accordingly.
The standard fault notification events are as follows:
Error frame event: The number of error frames in the time unit exceeds the
preset threshold.
Error frame second event: The number of seconds in which error frames occur
within the specified m seconds exceeds the preset threshold.
Error bit event: The number of error bits in the time unit exceeds the preset
threshold.
When the IEEE 802.3ah OAM protocol is enabled at a port, the protocol queries the
RMON statistic count on the hardware chip periodically to obtain the information
such as the number of correct packets and the number of error packets. After the
information is processed, you can find out whether the preceding three performance
events occur or not. If a certain performance event occurs, the peer equipment is
notified through an OAMPDU. After receiving the notification, the peer equipment
reports an ETHOAM_RMT_SD alarm.
OAMRemote Fault Detection
If the traffic is interrupted due to the equipment fault or equipment
unavailability, a notification is sent to the peer equipment through the
flag field in the OAMPDU.
Fault Symptom:
Link Fault: This fault is sent when the local port is shut down.
Dying Gasp: This fault is sent upon reboot or reset.
Critical Event: This fault is sent when a fault is received from the
OAM manager.
OAMRemote Loopback
Active
Passive
NE1 NE2
NE1 actively initiates a
remote loopback request.
After receiving a loopback request
packet from NE1, NE2 enters
loopback state, and then sends a
loopback response packet to NE1.
After receiving a loopback
response packet from NE2, NE1
enters loopback initiate state.
Loopback request packet sent by NE1
Loopback response packet sent by NE2
Only the active end can initiate a remote loopback request. If
the equipment at both ends initiates the remote loopback
request at the same time, the equipment with the larger MAC
address enters loopback state.

After entering loopback state, NE2 returns the packets (except
OAM packets) received on the loopback port to NE1.

NE1 sends test packets to detect the link. The MAC address,
packet length, and packet quantity can be specified. NE2
returns the test packets to NE1 without any change. NE1 then
counts the packet loss.

The loopback cancellation process is similar to the loopback
request process.
OAMSelf-Loop Check
This function can detect the self-loop from the transmit end of a
port to the receive end of the local port and the intra-board
loopback between two ports.
After the self-loop check is enabled on each port of the equipment,
the self-loop can be detected, and an ETHOAM_SELF_LOOP or
ETHOAM_VCG_SELF_LOOP alarm is reported.
The self-loop check function is developed by Huawei in
compliance with the IEEE 802.3ah protocol. With this function,
port loop problems can be solved by detecting and blocking self-
loop ports.
Appendix: Hardware and Supporting
Versions for the ETH-OAM Feature of RTN
Products
V100R002C00 and later All the versions IFX2
V100R002C00 and later All the versions IFU2
V100R002C00 and later All the versions EM6F
V100R002C00 and later All the versions EM6T
V100R005C00 and later All the versions EFP6
V100R003 and later All the versions EMS6 ETH-OAM
function
Applicable Product Version Applicable
Hardware Version
Applicable Board Feature
Name
Appendix: ETH-OAM Feature Specifications
of RTN Products (802.1ag)
Standard MP: 1000 ms/10000 ms/60000 ms/600000
ms
Common MP: 1000 ms to 60000 ms (at a step of 100
ms)
3.33 ms/10 ms/100
ms/1s/10s/1 min/10 min
CC Test
Transmit Period
(ms)
Standard MP (IEEE 802.1ag Draft 8.0)
Common MP (IEEE 802.1ag Draft 3.0)
Standard MP (IEEE
802.1ag Draft 8.0)
Supported MP
type
32 32
Number of
supported MPs
32 32
Number of
supported MAs
32 32
Number of
supported MDs
CC/LB/LT

CC/LB/LT
PING/AIS activation/
performance monitoring
OAM operation
EM6T/EM6F/IFU2/IFX2 EMS6/EFP6
Specification
Item
Appendix: ETH-OAM Feature
Specifications of RTN Products (802.3ah)
Active
Passive
Active
Passive
OAM mode
Yes Yes Monitoring on error
frame period events
frame second events
frame events
Auto-discovery
Remote loopback
Self-loop check
Auto-discovery
Link performance
monitoring
Remote fault
detection
Remote loopback
Self-loop check
OAM operation
EM6T/EM6F/IFU2/IFX2 EMS6/EFP6
Specification Item
Thank You
www.huawei.com

04-OptiX RTN Equipment ETH-OAM Feature-20100331-A

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

04-OptiX RTN Equipment ETH-OAM Feature-20100331-A

Uploaded by

Copyright:

Available Formats

www.huawei.

You might also like