4 - Ethernet Service

www.huawei.
com
Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.
Ethernet Principle
Service configuration
QOS
E-OAM
Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved. Page2
Contents
1. Ethernet Concept
2. Ethernet Port Technology
3. VLAN Basis
Do you know why IP address is
not fixed as MAC?
00000001 10111011 00111010 10111010 10111110 10101000
It means this is a multicast address.
Ethernet MAC Address
00.e0.fc.39.80.34
MAC address includes 48 bits and it is shown as 12 dotted
hexadecimal notations
MAC address is exclusive globally which is allotted and managed by
IEEE. Every MAC address is composed of two parts. The first 24 bits
part is the vendor code and the other 24 bits part is serial number
If 48 bits are all 1, it means the address is used for broadcast
If the 8th bit is 1, it means the address is used for multicast

Ethernet_II
DMAC SMAC Length/T DATA/PAD FCS
Length/Type
Mean
Length/T > 1500
Length/T <= 1500
Type of the frame
Length of the frame
802.3
46---1500 bytes
64---1518 bytes
Ethernet Frame Structure
Dest MAC Src MAC 8100 CXXX
C XXX
PPP m ID
0800 45 D
S
C
P
TLen F_ID Fr FO
TTL Pr

HCKS Dest IP Src IP MTU CRC
PPP VLAN priority, m = CFI not used, 45 = IPV4, 5byte frame
length , TLen = total frame length , F_ID = Frame ID , Fr = fragment
number , FO = Fragment offset , Pr = protocol , HCKS = header check
sum.
Precedance TOS
000 --- Routine 1000 ---- Minimize Delay
001 --- Priority 0100 ---- Maximize througput
010 --- Immediate 0010 ---- Maximize Reliability
011 --- Flash 0001 ---- Minimize Monetary Cost
100 --- Flash Override
101 --- CRITIC/ECP
110 --- Internetwork Contrl
111 --- Network Control
Ethernet Principle---CSMA/CD
CS: carrier sense
Sense before sending data to ensure the cable is idle and reduce
collision.
MA: multiple access
The data from every station can be received by other multiple stations.
CD: collision detection
Detect collision while sending data and stop it when the station find
collision then continue to send after waiting for a random time.
Physical
layer
Data link
layer
(BRIDGE/Ethernet switch/L2) equipment work
mode
L2 Work Mode
Application layer
Presentation layer
Conversation layer
Transport layer
Network layer
Data link layer
Physical layer
Physical
layer
L2 switch
Data link
layer
Application layer
Presentation layer
Conversation layer
Transport layer
Network layer
Data link layer
Physical layer
L2 Work Principle
Learning based on source
Segment 1
Segment 2
A
B
C
PORT
1
PORT
2
D
typical use of the switch
switch
MAC ADD. port
MAC A 1
MAC B 1
MAC C 2
MAC D 2
L2 Work Principle (Cont.)
Forwarding based on destination address

Port 1
Port 2
L2 Switch
MACD MACA
MACA MACD
MAC ADD. port
MAC A 1
MAC B 1
MAC C 2
MAC D 2
L2 Switch Principle
Receive all the data frames from the network segment
Save the source MAC addresses of the received frames to establish MAC
address table( self-learning based on source address) and maintain the
address table by aging mechanism
Check the MAC address table to find out the port corresponding to the
destination address. If it is the receiving port, it will take the frame; if it is
not the receiving port, the data will be broadcasted to all the other ports
(except the source port)
Forward broadcast and multicast frames to all other ports (except the
source port)
Three Switch Modes
Cut-Through
Switch forward the frame immediately after it receive destination address
Short time delay
Switch dont check the error
Store-and-Forward
Switch forward the frame after it receive the whole frame
Long time delay
Switch check the error so no error frame will be forwarded
Fragment-free
Switch forward the frame after it receive 64 bytes( the shortest frame length)
Integrate the advantage of the cut-through and store-and-forward mode

L2 will forward the received frames according to the MAC
address so collision domain is limited to one port. But it can not
limit the broadcast domain.
Broadcast Domain
SWITCH
LAN
LAN
LAN
LAN
LAN
Broadcast domain
collision domain
collision domain
collision domain
collision domain
collision domain
Contents
1. Ethernet Concept
3. VLAN Basis
Ethernet Connection Requirements
Ethernet connection must ensure the performance of the
network
Bandwidth
Delay
Two methods to increase bandwidth for users:
Increase the overall network bandwidth
Build switching Ethernet, and use bandwidth exclusively.
Increase link rate: 10M--100M--1000M
Decrease the number of equipment attached to the same shared
medium
Technical
Standard
Types of Cable
Transmission
Distance
100BaseTX 2 pairs EIA/TIA Type 5 (UTP) Unshielded Twisted Pair 100m
100BaseT4 4 pairs EIA/TIA Type 3, 4 and 5 (UTP) Unshielded Twisted Pair 100m
100BaseFX Multi-Mode Fiber (MMF) cable 550m-2km
1000BaseCX Copper shielded twisted-pair 25m
1000BaseT Copper EIA/TIA Category 5 (UTP) Unshielded twisted-pair, 4 pair 100m
1000BaseSX Multi-mode fiber, 50/62.5um fiber, use 850nm laser 550m/275m
EIA: Electronics Industries Association
TIA: Telecommunications Industries Association
Transmission Distance of Fast Ethernet
Contents
1. Ethernet Concept
3. VLAN Basis

Broadcast flooding is the main disadvantage of L2
switch
Disadvantage of Full Duplex and L2
Switch
Full duplex and L2 make Ethernet progress, resolve the
conflict problem and improve the Ethernet performance.
Furthermore the security is enhanced to some extent. But
the following disadvantages are still in the Ethernet:
Broadcast flooding
Security cant be guaranteed completely


Cause of VLAN Generation---
Broadcast Storm
broadcast
Broadcast domain1
VLAN 10
Broadcast domain2
VLAN 20
Broadcast domain3
VLAN 30
Engineering Department
Financial Department
Marketing Department
Prevent Broadcast Storm via
VLAN
Prevent Broadcast Storm
MAC VLAN
MAC A 5
MAC B 10
MAC C 5
MAC D 10
MAC A MAC B MAC C MAC D
Switch
Port VLAN
Port 1 5
Port 3 10
Port 7 5
Port 10 10
PC A PC B PC C PC D
Switch
Port 1
Port 3
Port 7
Port 10
VLAN Based on MAC or Port
Protocol VLAN
IPX 5
UDP 10
IP 2
. 11
IPX IP UDP IP
Switch
IP VLAN
1.1.1.1/24 5
1.1.2.1/24 10
1.1.3.1/24 2
. 11
1.1.1.1/24 1.1.2.1/24 1.1.3.1/24 2.1.1.1/24
Switch
VLAN Based on Protocol or Subnet
Frame Format of
VLAN
DA
SA
Type Data CRC
Standard Ethernet Frame
DA
SA Type Data CRC tag
TPID Priority
CFI VLAN ID
TCI
Ethernet Frame with IEEE802.IQ Flag
TPID
The TPID is a 2-byte field, and it identifies an Ethernet frame as a tagged frame. The value is always 0x8100. When the network
equipment that cannot identify the tagged frame receives the tagged frame, the equipment discards this frame.
> PCP
The priority code point (PCP). This field can be used to provide the requirement for the service quality.
> CFI
it is a 1-bit filed, and it is used in certain physical networks that adopt the ring topology. This field is not processed in the Ethernet.
l VID
The VLAN ID is a 12-bit field
VLAN 2 VLAN 1
VLAN 1 VLAN 2
Ethernet frame
with VLAN tag 1
Ethernet frame
with VLAN tag 2
Ethernet frame
without VLAN flag
Frame Changes in Network
Communication
Ethernet Card Port Tag Mode
Packets
Port
Tag flag Untag flag
Tag aware (In) Transmit transparently Drop
Tag aware (Out) Transmit transparently
Access (In) Drop
Attach a Tag flag (default VLAN
ID)
Access (Out)
Remove the Tag flag (default
VLAN ID)

Hybrid (In) Transmit transparently
Attach a Tag flag (default VLAN
ID)
Hybrid (Out)
If VLAN ID is the same, remove
the Tag flag, otherwise transmit
transparently

IF_ETH Port
Tag Attributes
The IF_ETH port is an internal Ethernet port on the Hybrid IF board. In the transmit direction of Hybrid microwave, the
Ethernet services transmitted to the MUX/DEMUX unit of the Hybrid IF board through the IF_ETH port and are then mapped
into the Hybrid microwave frames. In the receive direction of Hybrid microwave, the Ethernet services are demapped from
the Hybrid microwave frames and then transmitted to the packet switching unit through the IF_ETH port.
The main differences between the IF_ETH port and the GE/FE port are as follows:
>> The IF_ETH port is an internal Ethernet port. It transmits and receives MAC frames and does not have PHY-layer
functions.
>> The bandwidth over the IF_ETH port is equal to the Ethernet service bandwidth that the Hybrid microwave supports.
Hence, when the AM function is enabled in the case of Hybrid microwave, the bandwidth over the IF_ETH port changes
according to the modulation mode.
In the case of OptiX RTN 950, the VLAN
tag is closely related to Encapsulation
Type.
>> When Encapsulation Type is set to
Null or QinQ, the VLAN tag is invalid.
>> When Encapsulation Type is set to
802.1Q, the VLAN tag can be set to Tag
Aware, Access, or Hybrid.
QinQ
> Ethernet frame with only a C-TAG the tagged frame defined in IEEE 802.1Q.
> Format of the Ethernet frame with a C-TAG and an S-TAG the value of the TPID in the S-TAG is 0x88a8, whereas
the value of the TPID in the C-TAG is 0x8100.

> Format of the Ethernet frame with only an S-TAG
Network Attributes
The network attribute of each port can be set to UNI and NNI depending on how the port processes the C-TAG and S-TAG.
)) UNI
By default, the UNI considers that the received frames do not carry any S-TAG. According to Encapsulation Type of
Ethernet ports, the UNI is classified into two types:
Ports whose Encapsulation Type is Null
This port does not check the VLAN tags. Hence, all types of Ethernet frames can enter this port. This port supports the
creation of PORT-based QinQ services and does not support the creation of PORT+CVLAN-based QinQ services.
Ports whose Encapsulation Type is 802.1Q
In the case of QinQ services, when Encapsulation Type is 802.1Q, Tag must be set to Tag Aware. In this case, the port
checks the outer VLAN tag that the Ethernet frames carry, and processes the outer VLAN tag as the C-VLAN tag. Hence,
untagged frames cannot enter this port. This port supports the creation of both PORT-based QinQ services and
PORT+CVLAN-based QinQ services.
)) NNI
By default, the NNI considers that the received frames carry the S-TAG. When Encapsulation Type is QinQ, the
Ethernet port is an NNI. Only the NNI can be used to configure the QinQ link.
E-Line Services
QinQ-based
E-Line service
UNI-UNI
Null (source)
Null (sink)
802.1Q (source)
802.1Q (sink)
Point-to-point transparently
transmitted E-Line service
VLAN-based
E-Line service
UNI-NNI
NNI-NNI
Null (source)
QinQ (sink)
802.1Q (source)
QinQ (sink)
QinQ (source)
QinQ (sink)
T
r
a
f
f
i
c

F
l
o
w

PORT (source)
PORT (sink)
[ source port transparently
transmits all the received
Ethernet frames to the
sink port.]
E
n
c
a
p
s
u
l
a
t
i
o
n

[ source and Sink ports
processes the received
Ethernet frames according
to the tag attributes of
the Ethernet frames ]
PORT (source)
PORT (sink)
PORT+VLAN (source)
PORT+VLAN (sink)
[ source and Sink ports
processes the received
Ethernet frames according to the
[ tag attributes + comparison of
Filtering table with traffic C-VLAN ]
PORT (source)
QinQ link (sink)
[ source port adds
the SVLAN tag that
corresponds to the
QinQ link into all the
Ethernet frames ]
PORT (source)
QinQ link (sink)

[ source port accesses only
the Ethernet frames that
carry VLAN tags. It adds the
SVLAN tag that corresponds
to the QinQ link into all the
Ethernet frames ]
PORT+CVLAN (source)
QinQ link (sink)
[ The source port adds the
SVLAN tag that corresponds
to the QinQ link into all the
Ethernet frames that carry
the specific CVLAN tag
A.Ethernet Private Line, B- Ethernet Private LAN.
A-EPL Ethernet Private Line Point to Point Communication.
Three major Mechanisms:-
A.1-EPL Transparent,

Direction
Encapsulation Flow
UNI - UNI NULL - NULL Port [ Source] Port [ Sink ]

MAC1
MAC2
MAC2
MAC3
MAC3

A.2-EPL 802.1Q,

NO
Direction Encapsulation Flow
1- UNI - UNI 802.1Q - 802.1Q Port [Source] Port [Sink]
2- UNI - UNI 802.1Q - 802.1Q Port+CVLAN [Source] Port+ CVLAN [Sink]
802.1Q

802.1Q
802.1Q
802.1Q

802.1Q

802.1Q
MAC1
MAC1
MAC2
MAC2
MAC3
MAC3
MAC1
A.3-EPL QinQ,
Direction Encapsulation Flow
1- UNI - NNI NULL - QinQ Port [Source] QinQ [Sink]
2- UNI - NNI 802.1Q - QinQ Port [Source] QinQ [Sink]
3- UNI - NNI 802.1Q - QinQ Port+CVLAN [Source] QinQ [Sink]
4- NNI - NNI QinQ- QinQ Port+SVLAN [Source] Port+ SVLAN [Sink]
MAC1
MAC1
MAC2
MAC2
MAC3
MAC3
S-VLAN1
S-VLAN2
802.1Q

802.1Q
802.1Q

802.1Q

802.1Q

802.1Q

S-VLAN1
S-VLAN2
S-VLAN1
S-VLAN2
MAC1
MAC5
MAC3
MAC1
MAC2
MAC3
MAC4
MAC5
MAC4
MAC2
QinQ link (source)
QinQ link (sink)
The source port transmits the Ethernet frames that carry the SVLAN tags that correspond to the source
QinQ link to the sink port where the sink QinQ link is configured. If the source and sink QinQ links
correspond to different SVLAN tags, the SVLAN tags carried in the Ethernet frames are exchanged.
In the case of VLAN-based E-Line service models, the same VLAN tag generally needs to be configured for the source and sink.
That is, the VLAN tag carried in the frames transmitted from the source should be the same as the VLAN tag carried in the frames
received at the sink. If the frames need to carry different VLAN tags at the source and sink, you need to configure the VLAN
forwarding table except in the case of an E-Line service wherein different VLAN tags are configured for the service source and sink.
After the VLAN forwarding table is configured, the VLAN tags of the service source and sink are switched.
VLAN Forwarding Table
E-LAN Services
Bridge
> Shared VLAN learning (SVL)
it creates an entry according to the source MAC address and the source port of a packet. This entry is valid to all VLAN tags.
> Independent VLAN learning (IVL)
The entry is according to the source MAC address, VLAN ID, and source port of a packet. This entry is valid to only this VLAN tag.
bridge is available in three types, [ 802.1d, 802.1q, and 802.1ad ].
The switching domain of the bridge can be divided into several independent sub switching domains in different domain switching
modes using the concept of Logical Port.
The logical port may be based on PORT, PORT+VLAN, PORT +CVLAN, or PORT+SVLAN. That is, a physical port can be mapped
into several logical ports, which can be in the same sub switching domain or in different sub switching domains.
Bridge Type
802.1d Bridge
IVL
PORT
802.1q Bridge 802.1ad Bridge
SVL
B
r
o
a
d
c
a
s
t

d
o
m
a
i
n

T
y
p
e

o
f

l
o
g
i
c
a
l

p
o
r
t

PORT+VLAN
PORT or
PORT+CVLAN (UNI)
PORT+SVLAN (UNI,NNI)
Entire bridge All the logical ports whose VLAN tag
is the same as the VLAN tag carried
in the Ethernet frame
All the logical ports whose SVLAN tag
is the same as the SVLAN tag carried
in the Ethernet frame
IEEE 802.1d
Bridge-Based ELAN Service
IEEE 802.1q
Bridge-Based ELAN Service
E
n
c
a
p
s
u
l
a
t
i
o
n

t
y
p
e

T
a
g

t
y
p
e

Tag-Transparent
Null
C-Awared S-Awared
Null or 802.1Q
Null or 802.1Q(UNI)Tage Aware
QinQ (NNI)
IEEE 802.1ad Bridge-Based ELAN
Service
Configuration Example (Point-to-Point Transparently Transmitted E-Line Services)
Configuration Example (VLAN-Based E-Line Service)
NE1 NE2
NE3 NE4
NE1
NE2
NE1
Configuration Example (QinQ-Based E-Line Service)
The VLANs used by the services on a BTS is
allocated by the BTS. Hence, the VLANs of
services on different BTSs may be the same. To
solve this problem, the BSC allocates an S-
VLAN for each BTS, and the S-VLANs on the
entire network are planned in a unified manner,
NOTE
In this example, the BSC needs to be capable of
processing the S-VLAN tag.
NE2
In this example, the SVLAN T-PID that the BSC can identify is 0x8100. Hence,
you need to set QinQ Type Domain to 0x8100 for the two GE ports connecting
to the BSC. The other NNI ports connect to internal equipment. Hence, you
need to set QinQ Type Domain to 0x88a8 for the other NNI ports.
NE1
If the Ethernet services on each BTS do not contain any untagged frames, you
can set Encapsulation Type to 802.1Q and set Tag to Tag Aware for the FE
port that accesses the Ethernet services on each BTS.
The IF_ETH ports connect to internal equipment. Hence, you need to set QinQ
Type Domain to 0x88a8 for the IF_ETH ports.
NE1
NE2
NE1
Configurations of Various Services
P2P/VLAN E-Line QinQ-Based E-
Line
IEEE 802.1d bridge-
based E-LAN
IEEE 802.1q bridge-
based E-LAN
IEEE 802.1ad bridge-
based E-LAN
1
Setting the
parameters of
Ethernet ports
Setting the
parameters of
Ethernet ports
Setting the
parameters of
Ethernet ports
Setting the
parameters of
Ethernet ports
Setting the
parameters of
Ethernet ports
2
Setting the
parameters of
the IF_ETH
ports
Setting the
parameters of
the IF_ETH
ports
Setting the
parameters of
the IF_ETH
ports
Setting the
parameters of the
IF_ETH ports
Setting the
parameters of the
IF_ETH ports
3
Configuring
the LAG
Configuring
the LAG
Configuring the
LAG
Configuring the
LAG
Configuring the
LAG

4
Configuring
the E-Line
Configuring
the QinQ Link
Configuring the
ERPS
Configuring the
ERPS
Configuring the
ERPS

5
Configuring
the QoS
Configuring
the E-Line
Configuring the
E-LAN
Configuring the E-
LAN
Configuring the E-
LAN
6
Verifying
Ethernet
service
configurations
Configuring
the QoS
Configuring the
QoS
Configuring the
QoS
Configuring the
QoS

7
Verifying
Ethernet
service
configurations
Verifying
Ethernet service
configurations
Verifying Ethernet
service
configurations
Verifying Ethernet
service
configurations
Note:
indicates that the configuration item is optional. Configure the services according to the service
requirements.
Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.
Page40
The source port processes the incoming Ethernet frames
based on its TAG attribute, and then sends the processed
Ethernet frames to the sink port. The sink port processes the
Ethernet frames based on its TAG attribute, and then exports
the processed Ethernet frames.
The source port processes the incoming Ethernet frames
based on its TAG attribute, and then sends the Ethernet
frames with a specific VLAN ID to the sink port. The sink port
processes the Ethernet frames based on its TAG attribute,
and then exports the processed Ethernet frames.
Configurations of Ethernet
Services
Setting the Parameters of Ethernet Ports
Setting the Parameters of IF_ETH Ports
Configuring the LAG
Configuring the QinQ Link
Configuring the E-Line Service
Configuring the ERPS
Configuring the E-LAN Service
Configuring the QoS
Verifying Ethernet Service Configurations
Setting the Parameters of Ethernet
Ports
Configuring the
traffic control
Setting the
advanced
attributes
Setting
general
attributes
P2P E-Line services:
VLAN-based E-Line
services:
QinQ-based E-Line services:
Setting the layer
2 attributes
Configuring the
traffic control
Setting the
advanced
attributes
Setting
general
attributes
Configuring the
traffic control
Setting the
advanced
attributes
Setting
general
attributes
IEEE 802.1d bridge-
based E-LAN services:

IEEE 802.1q bridge-based
E-LAN services:
IEEE 802.1ad bridge-based
E-LAN services:
Setting the layer
2 attributes
Configuring the
traffic control
Setting the
advanced
attributes
Setting
general
attributes
Setting the layer 2
attributes
Configuring the
traffic control
Setting the
advanced
attributes
Setting general
attributes
Ports

Ports on an
Ethernet board
IF_ETH ports
Setting the layer
2 attributes
Configuring the
traffic control
Setting the
advanced
attributes
Setting general
attributes
The general attributes of an Ethernet port define the physical-layer information, such as the port mode,
encapsulation type, and maximum frame length.
In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled.
Encapsulation Type
In the case of P2P E-Line services and IEEE 802.1d bridge-based E-LAN services, set Encapsulation Type to Null.
In the case of VLAN-based E-Line services and IEEE 802.1d bridge-based E-LAN services, set Encapsulation Type to
802.1q.
In the case of QinQ-based E-Line services and IEEE 802.1ad bridge-based E-LAN services, if a UNI can access untagged
frames, set Encapsulation Type to NULL. If a UNI can access tagged frames only, set Encapsulation Type to 802.1q. In the
case of an NNI port, set Encapsulation Type to QinQ.
In the case of an Ethernet port that is connected to the external equipment, set Working Mode to a value the same as that of
the external equipment. (Generally, Working Mode of the external equipment is set to Auto-Negotiation. In the case of the
Ethernet ports within the network, set Working Mode to Auto-Negotiation.
When JUMBO frames are transmitted, set Max Frame Length (byte) according to the actual length of the JUMBO frames.
Otherwise, it is recommended that you set Max Frame Length (byte) to 1536.
Ports

After the traffic control is enabled, if the link is congested, the Ethernet port sends the PAUSE frame to
notify the peer end of stopping the transmission of Ethernet packets for a period, thus eliminating the
link congestion.
Required when the flow control function is enabled on the external equipment to which the Ethernet
port is connected. Set the parameters as follows:
When the external equipment uses the non-auto-negotiation flow control function, set Non-
Autonegotiation Flow Control Mode to Enable Symmetric Flow Control.
When the external equipment uses the auto-negotiation flow control function, set Auto-
Negotiation Flow Control Mode to Enable Symmetric Flow Control.

Setting the layer
2 attributes
Configuring the
traffic control
Setting the
advanced
attributes
Setting general
attributes
For P2P E-Line services and IEEE 802.1d bridge-based E-LAN services: You do not need to set the layer 2 attributes.
For VLAN-based E-Line services and IEEE 802.1 bridge-based E-LAN services: If all the accessed services carry VLAN
tags (tagged frames), set Tag to Tag Aware. If none of the accessed services carries VLAN tags (untagged frames), set
Tag to Access. If the access services contain both tagged frames and untagged frames, set Tag to Hybrid. Set Default
VLAN ID and VLAN Priority according to the network planning information.
For QinQ-based E-Line services and IEEE 802.1ad bridge-based E-LAN services: In the case of a UNI port, if
Encapsulation Type is set to 802.1q, Tag must be set to Tag Aware (default value). In the case of an NNI port that is
connected to the external equipment, set QinQ Type Domain according to the T-PID of the SVLAN that is supported by the
external equipment. In the case of an NNI port within the network, set QinQ Type Domain to the default value.
Setting the layer
2 attributes
Configuring the
traffic control
Setting the
advanced
attributes
Setting general
attributes
The advanced attributes of Ethernet ports are used to configure the MAC/PHY loopback and query the traffic rate on the
ports.
Required when you need to enable the port self-loop test and automatic loopback shutdown functions or to enable the
broadcast packet suppression function. Set Loopback Check, Loopback Port Shutdown, Enabling Broadcast Packet
Suppression, and Broadcast Packet Suppression Threshold according to the requirements.
Setting the layer
2 attributes
Configuring the
traffic control
Setting the
advanced
attributes
Setting general
attributes
Services
Configuring the LAG
Configuring the QoS
Setting the layer
2 attributes
Setting the
advanced
attributes
Setting general
attributes

Encapsulation Type
In the case of P2P E-Line services and IEEE 802.1d bridge-based E-LAN services, set
Encapsulation Type to Null.
In the case of VLAN-based E-Line services and IEEE 802.1d bridge-based E-LAN services,
set Encapsulation Type to 802.1q
In the case of QinQ-based E-Line services and IEEE 802.1ad bridge-based E-LAN services,
if a UNI can access untagged frames, set Encapsulation Type to NULL. If a UNI can access
tagged frames only, set Encapsulation Type to 802.1q. In the case of an NNI port, set
Encapsulation Type to QinQ
The Layer 2 attributes of the IF-ETH port specify the relevant information about the link layer, including the
tag attribute and QinQ type domain.
Setting the layer
2 attributes
Setting the
advanced
attributes
Setting general
attributes
For P2P E-Line services and IEEE 802.1d bridge-based E-LAN services: You do not need to set the
layer 2 attributes.
For VLAN-based E-Line services and IEEE 802.1 bridge-based E-LAN services: If all the accessed
services carry VLAN tags (tagged frames), set Tag to Tag Aware. If none of the accessed services carries
VLAN tags (untagged frames), set Tag to Access. If the access services contain both tagged frames and
untagged frames, set Tag to Hybrid. Set Default VLAN ID and VLAN Priority according to the network
planning information.
For QinQ-based E-Line services and IEEE 802.1ad bridge-based E-LAN services: In the case of a UNI
port, if Encapsulation Type is set to 802.1q, Tag must be set to Tag Aware (default value). In the case of
an NNI port that is connected to the external equipment, set QinQ Type Domain according to the T-PID of
the SVLAN that is supported by the external equipment. In the case of an NNI port within the network, set
QinQ Type Domain to the default value.
When the IF_ETH port transmits an Ethernet service that permits bit errors, such as a voice service or
a video service, you can set Error Frame Discard to Disabled.
Setting the Parameters of IF_ETH
Ports
Setting the layer
2 attributes
Setting the
advanced
attributes
Setting general
attributes
Services
Configuring the LAG
Configuring the QoS
Configuring the QinQ link is prerequisite for configuring QinQ private line services and 802.1ad bridge
services.

QinQ Link ID specifies the ID of a QinQ link. Value range: 1 to 4294967295.
Board specifies the board that carries the QinQ link. The Encapsulation Type
of the port must be set to QinQ during the configuration of port parameters.
Port specifies the port that carries the QinQ link. The Encapsulation Type of
the port must be set to QinQ during the configuration of port parameters.
S-Vlan ID specifies the VLAN ID (at the network operator side) for the QinQ
link. This parameter is set according to the planning information.
Services
Configuring the LAG
Configuring the QoS

Configuring the P2P Transparently Transmitted E-Line
Service (1)
Set Service ID/Service
Name according to the
design.
Set Direction to UNI-
UNI. Except for QinQ-
based E-Line services,
select UNI-UNI for all the
other E-Line services.
Select a source port and
a sink port. Select a board
from the Board drop-down
list, and then select an
available port.
The values of the
Encapsulation Type parameter
of the ports must be the same.
Configuring the P2P Transparently Transmitted E-
Line Service (2)
Configuring the VLAN-Based E-
Line Service (1)
design.
Set Direction to UNI-
UNI. Except for QinQ-
based E-Line services,
select UNI-UNI for all the
other E-Line services.
a sink port. Then, configure
the source VLAN and the
sink VLAN.
a sink port. Select a board
from the Board drop-down
list, and then select an
available port.
The values of the
Encapsulation Type parameter
of the ports must be the same.

After the corresponding
VLAN forwarding table item
is created, the VLAN IDs of
the service packets can be
switched at the source or
sink end of the E-Line
service. If the VLAN IDs at
both the source end and the
sink end are the same, you
do not need to create the
VLAN forwarding table item.
Configuring the VLAN-Based E-
Line Service (2)
Configuring the QinQ-Based E-
Line Service (1)
Click Sink. In the dialog
box that is displayed,
select the selected QinQ
link and click OK.
If you forgot to create a
QinQ link, create one by
clicking Create QinQ Link.
Name according to the design.
Set Direction to UNI-UNI or
NNI-NNI. UNI-NNI indicates
that services are accessed
through ports to the QinQ link.
Both source and sink of NNI-
NNI are the QinQ Link.
Select a source port and a
sink port. If Direction is set to
UNI-UNI, the source is a port
and the sink is the QinQ link. If
Direction to NNI-NNI, both the
source and the sink are QinQ
link.
Configuring the QinQ-Based E-
Line Services (2)
A- Split Horizon Group Service level for loop prevention
To isolate services and to prevent broadcast storms due to a service loop, The logical ports that are assigned in the same split
horizon group cannot forward frames to each other.

When the ERPS protection is enabled for the ring
network, the ERPS protocol ensures that no
service loop is generated. If the split horizon
group is configured in this case, it affects the
ERPS protection.
The OptiX RTN 950 supports only the split horizon
group that is configured according the physical ports.
Hence, if one of the logical ports that correspond to a
physical port is configured as a member of a split
horizon group, the other logical ports are automatically
added to the split horizon group.
B- Management of the MAC Address Table
Entries of a MAC address table provide the mapping relations between MAC addresses and ports. The entries can be classified into
the following categories:
> Dynamic entry
Obtained through the SVL/IVL mode. The dynamic entry may age or lost after the packet switching unit is reset.
The aging time of a MAC address table is five minutes by default. The OptiX RTN 950 supports enabling/disabling the aging function
and setting the aging time for the MAC address table.
> Static entry
A static entry, which corresponds to a specific MAC address and port, is manually added by the network administrator into the MAC
address table by using the NMS. The static entry does not age, and is also not lost after the packet switching unit is reset. It is
needed when MAC address is known, and on which there is large volume of traffic for a long time.
> Blacklist entry
A blacklist entry is used to discard the data frame that contains the specified MAC address, namely, The blackhole entry does not
age, and is also not lost after the packet switching unit is reset.
C- Protection for Ethernet Services
1- Ethernet ring protection switching (ERPS),
2- link aggregation (LAG),
3- multiple spanning tree protocol (MSTP).
ERPS
can provide protection for the E-LAN services between all the nodes on the ring network.
RPL node
Protection Instance Protection Type R-APS Message R-APS Timer Switching Condition
Switching Impact Availability
Relation with Other Features Realization Principle
Refer to appendix-A for detailed description of above items.
Services
Configuring the LAG
Configuring the QoS

Set ERPS ID according to the design. The ERPS ID
must be unique. The value of ERPS ID ranges from 1
to 8.
East/West port: specifies the east/west port of the
ERPS instance.
RPLOwner Ring Node Flag: specifies whether a
node on the ring is the ring protection link (RPL) owner.
Only one node on the Ethernet ring can be set as the
RPL owner.
RPL Port: specifies the RPL port.
Control VLAN: specifies the VLAN ID of Control
VLAN. Each node on the Ethernet ring transmits the R-
APS packets on the dedicated ring APS (R-APS)
channel to ensure consistency between the nodes
when the ERPS switching is performed. Control VLAN
is used for isolating the dedicated R-APS channel.
Therefore, the VLAN ID in Control VLAN cannot be
duplicate with the VLAN IDs that are contained in the
service packets or inband DCN packets.
Destination Node: displays the MAC address of the
destination node. The default destination MAC address
in the R-APS packets is always 01-19-A7-00-00-01.
Hold-Off Time: specifies the hold-off time of the ERPS
hold-off timer. If only the ERPS exists, set this parameter
to 0. If the ERPS coexists with the LAG protection, set
this parameter to 500 ms.
Guard Time: specifies the guard time of the EPRS
guard timer. It is recommended that you use the default
value 500 ms.
Entity Level: specifies the level of the maintenance
entity according to the design.
WTR Time: specifies the WTR time of the WTR
timer in the case of ERPS protection. It is
recommended that you use the default value 5.
Packet Transmit Interval: specifies the interval
for transmitting the R-APS packets. It is
recommended that you use the default value 5.
>noRB: The RPL is not blocked.
>RB (RPL Blocked): The RPL is blocked.
> noDNF: The R-APS packets do not contain the DNF
flag. In this case, the packets are forwarded by the node
that detects the fault on a non-RPL link, and the node that
receives the packets is requested to clear the forwarding
address table.
> DNF: not to clear the forwarding address table.
Idle: = normal state
Protection: : = other transition state
the MAC address
of the source node
that initiates the
switching request.
LAG
LAG provides the following functions:
Increased bandwidth
aggregation module distributes the traffic to different members
by using the load sharing algorithm, thus realizing the load sharing function at the link level.

> increased availability
The links in a LAG dynamically back up each other. When a link fails, another link in
the LAG quickly replaces the faulty link.
LAG Types Port Types Switching Condition Availability Relation with Other Features
By aggregation type, >> [ manual aggregation and static aggregation.]
By load type, >> [ load sharing and load non-sharing.]
LAG Types
## Manual aggregation
When a user adds or deletes a member port, the LACP protocol
is not started. A port is in the up or down state. The system
determines whether to perform aggregation depending on the
physical status of a port (up or down).
## Static aggregation
When a user adds or deletes a member port, the LACP
protocol is started. A port can be in the selected or
standby state.
The LACP protocol determines the active and inactive
links in the aggregation group. Static aggregation is more
accurate and more effective than manual aggregation in
controlling link aggregation.
$$ Load sharing
Each member link in a LAG carries traffic. That is, the member
links in the LAG share the load. When a member in a
LAG changes or a certain link fails, the traffic is re-allocated
automatically.
The load sharing algorithms are as follows:
AUTO
Based on MAC addresses, including the source MAC
address, destination MAC address, and source MAC
address Xor destination MAC address.
Based on IP addresses, including the source IP address,
destination IP address, and source IP address Xor
destination IP address.
> Load non-sharing
Only one member link in a LAG carries traffic and the other links
in the LAG are in the standby state. This is equivalent to 1:N
But OptiX RTN 950 can be configured with only one active link
and one standby link.In this mode, the LAG can be set to
revertive or non-revertive.
Port Types
MAIN PORT
> it represents the LAG to participate in service configuration.
> A LAG has exactly one main port.

> The main port can either in the selected state [the port can bear
services] or in the standby state [the port cannot bear services],
independent of the port status.

The main port must be in the affiliated aggregation group until the
aggregation group is deleted.

> When the aggregation group is deleted, all the services in the
aggregation group continue to exist on the main port and no services
are lost.
SLAVE PORT
> The slave port cannot participate in service configuration.

> A LAG can have several slave ports.

> The slave port can either in the selected state [bear
service] or in the standby state [does not bear service].

> A slave port can be added to/deleted dynamically from the
LAG by using the NMS.
Switching Condition
Switching Impact
not longer than 500 ms),
Availability EM6T , EM6F , IFU2 , IFX2
> When you create a 1+1 HSB/FD/SD protection group of the
Hybrid radio, the NE automatically creates a LAG in non-load
sharing mode. The main port is the IF_ETH port on the main IF
board and the slave port is the IF_ETH port on the standby IF
board. The LAG is not displayed on the NMS and cannot be
configured manually.

> When you create an N+1 protection group of the Hybrid radio,
the NE automatically creates a LAG in load sharing mode. By
default, the main port is the IF_ETH port on the IF board
with the smallest slot ID. The LAG is not displayed on the NMS
and cannot be configured manually.

> When you create one XPIC protection group of the Hybrid
radio, manually create the LAG because the NE does not
automatically create a corresponding LAG.

> One LAG can be a member of an MSTP port group.

> One LAG can be a member of an IGMP Snooping multicast
group.

> Air interfaces can be configured into a LAG. The AM attribute,
channel spacing, modulation scheme, and preset number of E1
services must be set to the same values for the two IF ports in a
LAG.

> Ethernet ports of the same type can be aggregated into a
LAG. FE ports and GE ports cannot be aggregated.
Relation with Other Features
Services
Configuring the LAG
Configuring the QoS
Configuring the LAG
Link aggregation allows multiple links that are attached to the same equipment to be aggregated to
form a link aggregation group (LAG) so that the bandwidths and availability of the links increase. The
aggregated links can be considered as a single logical link. Required if the LAG is configured to
protect the FE/GE ports or if the Hybrid radio uses the N+0/XPIC configuration mode.

Configuring the LAG
Manually enter the number of the LAG. This parameter
is valid only when Automatically Assign is not selected.
Set the name of the LAG. It is recommended that you
set LAG Name in a form of LAG_No.
Set LAG Type to the same value as the opposite equipment.
Generally, set LAG Type to Static for the equipment at both ends.
In the case of FE/GE ports, set Load Sharing to the same value
as the opposite equipment. If the LAG is configured only to realize
protection, it is commended that you set Load Sharing to Non-
Sharing for the equipment at both ends. If the LAG is configured to
increase the bandwidth, it is recommended that you set Load
Sharing to Sharing for the equipment at both ends. When the
Hybrid microwave uses the N+0/XPIC configuration mode, set Load
Sharing to Sharing for the equipment at both ends.
Set Revertive Mode to the same value as the opposite
equipment. Generally, set Revertive Mode to Revertive for the
equipment at both ends. This parameter is valid to only LAGs
whose
Set Load Sharing to Non-Sharing. Set System Priority to the
default value. This parameter is valid to only static LAGs.
Set Main Board, Main Port, and Selected Slave Ports
according to the planning information. It is recommended that you
set this parameter to the same value for the main and slave ports
of the LAGs at both ends. The Hybrid/AM attributes of the IF ports
in the LAGs must be the same.
Configuring the LAG
Port Priority indicates the priorities of the ports in a LAG as defined in the LACP
protocol. The smaller the value, the higher the priority. When ports are added into a
LAG, the port of the highest priority is preferred for service transmission.

Set System Load Sharing Hash Algorithm to the same value as that of the opposite
equipment. Unless otherwise specified, this parameter takes the default value. This
parameter is valid to only LAGs whose Load Sharing is set to Sharing. The load sharing
computation methods include:MAC address specific allocation (based on the source MAC
address, destination MAC address, and XOR between source MAC address and source
MAC address), IP address specific allocation (based on the source IP address, destination
IP address, and XOR between source IP address and destination IP address).
MSTP MSTP maximizes the usage of link bandwidths by setting up several independent spanning trees.
The spanning tree topology can be configured in the case of a bridge
fault or a route interruption. In this manner, protection is provided.
Temporary data loops can be prevented by automatically accepting the
bridges and ports of the bridges that are newly added into the LAN.

> A small part of the available link bandwidths is used to create or
maintain the spanning tree, and the bandwidth does not increase with the
expanding network scale.

> The MSTP classifies a switching network into different regions.
Each region is called an MST region. Within each region, multiple
spanning trees exist and they are independent from each other.
Each spanning tree is called a multiple spanning tree instance
(MSTI).

> In the case of the MSTP, the VLAN mapping table is configured to
specify the mapping relations between VLANs and MSTIs. Within an
MST region, each VLAN corresponds to one MSTI. That is, the data
from the same VLAN can be transmitted only on the same MSTI.
One MSTI, however, may correspond to multiple VLANs.
MSTI
VLAN2
VLAN1
VLAN3
MST
MSTI
VLAN
> MSTI 1 uses switch A as the root
switch to forward packets of VLAN 1.

> MSTI 2 uses switch C as the root
switch to forward packets of VLAN 2.
MSTI1 > VLAN1
MSTI2 > VLAN2
Optix-910 and 950 supports only CIST.
For more data refer to appendix A.
Configuration Example (802.1d-Bridge-Based E-LAN Service)
NE1
In this example, all the services are aggregated on NE1. Hence,
the NE that is farthest from NE1 needs to function as the RPL
owner. In this way, when the ring network is normal, the traffic
carried on each link is relatively even.
In this example, ERPS is adopted to prevent network loop.
Therefore, the split horizon group cannot be used.
Services
Configuring the LAG
Configuring the QoS

Configuring the 802.1d Bridge-
Based E-LAN Service (1)
design.
Select Tag-Transparent
from the Tag Type drop-down
list.
Set whether to enable the
MAC address self-learning
function. If the MAC self-
learning function of an
Ethernet LAN is enabled, the
Ethernet LAN learns an MAC
address according to the
original MAC address in the
packet and automatically
refreshes the MAC address
forwarding table.
Select a board from the
Board drop-down list.
Select a port of the board. Click
the right arrow to add the selected
port to the list of selected ports.
Configured
ports
Click Next.
Create a split horizon
group as required.
Select Split Horizon
Group to create a split
horizon group as required.
Split Horizon Group ID:
The default value is 1. It
cannot be set manually.
Split Horizon Group
Member: The port members
that are added to the same
split horizon group cannot
communicate with each other.
Configuration Example (802.1q-Bridge-Based E-LAN Service) NE1
Configuring the 802.1q Bridge-
design.
Select C-Awared from the
Tag Type drop-down list.
forwarding table.
Configure the UNI port. Select a board from the
Board drop-down list, and then select a port.
Set VLAN of each port according to the design.
The port members that are
added to the same split
horizon group cannot
Configuration Example (802.1ad-Bridge-Based E-LAN Service)
> Each BTS independently plans VLANs for its services.
> The BSC needs to be capable of processing the S-VLAN tag.
> The BSC allocates an S-VLAN to each BTS, and the S-VLANs on the
entire network are planned in a unified manner.
> The Ethernet services on the ring network need to be protected.
NE1
NE2
Configuring the 802.1ad Bridge-
In the case of the 802.1ad
bridge-based E-LAN
services, configure the UNI
port and the NNI port.
Configure the UNI port first.
design.
Select S-Awared from the
Tag Type drop-down list.
forwarding table.
Set S-VLAN of each port according to the design.
Set S-VLAN of each port according to the design.
The port members that are
added to the same split
horizon group cannot
Mixed Study configuration case
Untagged traffic
10 Mbps
Tagged V2 traffic
10 Mbps
Tagged V3 traffic
10 Mbps
Tagged V4 traffic
10 Mbps
2E1 services
Configuration scenarios:-

1- NE1NE2 BW = 50 M.
RNC supposed to receive aggregated traffic of Vlan-2 from
Node-B_1 and Node-B_2 with rate 20 MBps.

2- NE1---NE2 BW has been reduced to 40M due to
AM-DOWNSHIFT with V3 , V4 has the hier priorities.

NE2
NE1
NE3
NE4
Appendix A [ ERPS ] Protection Instance
Ethernet ring node, ring link, ring protection link (RPL), RPL
owner, and east (E) ports and west (W) ports
at each Ethernet ring node are defined.
Only one RPL is available on one Ethernet ring.
A ring port can be an FE port, a GE port, or a radio port.
The OptiX RTN 950 does not support Ethernet tangent rings or Ethernet
intersecting rings. That is, different protection instances of the ERPS cannot
contain one or more same ring ports.
Protection Type The ERPS is revertive.
R-APS Message
01-19-A7-00-00-01.
>> The ring nodes transmit R-APS messages on the specific R-APS channel to
ensure that all the ring nodes perform consistent operations to complete the ERPS.
The frame format of the R-APS message is a type of ETH-OAM frame formats.

>> An R-APS message uses afixed default MAC destination address,

>> An R-APS message also contains a VLAN ID, which identifies an R-APS
message from the Ethernet service message and inband DCN message.

>> Through different VLAN IDs, R-APS messages and Ethernet service messages
can be separately transmitted over isolated VLAN channels.

>> To prevent messages from forming loops, the blocked ports on the R-APS
channel and on the Ethernet service channel must be the same. That is, the same
ring port is blocked for the R-APS channel and the Ethernet service channel.
> R-APS (SF) message: A node detecting an SF condition
transmits the R-APS (SF) message. The other ring nodes that
receive the R-APS (SF) message are informed that a remote node
is faulty.

> R-APS (NR, RB) message: The RPL owner transmits the R-APS
(NR, RB) message. The other ring nodes that receive the R-APS
(NR, RB) message are informed that the Ethernet
ring is normal and the RPL connection point on the remote RPL
owner is blocked.

> R-APS (NR) message: A node that detects fault recovery
transmits the R-APS (NR) message. Nodes that receive the R_APS
(NR) message are informed that the switching trigger condition at
the remote end is cleared.

If an R-APS message contains the DNF flag (that is, the value of the
DNF field is equal to 1), a node that detects the fault on the RPL
transmits this message. The node that receives this message is
informed that it should not empty the MAC address table.
R-APS Timer
Guard Timer WTR Timer
Holdoff Timer
is used to prevent ring nodes from receiving
outdated R-APS messages. When a faulty
node detects that the switching condition is
cleared, it starts the guard timer and starts
to forward the R-APS (NR) message. When
the guard timer is running, the ring node
discards the R-APS message that arrives.
When the guard timer expires, the received
R-APS message is forwarded.
10 ms steps between 10 ms and 2s, with a
default value of 500 ms.

When the former working channel
is restored to normal, the WTR timer
on the RPL owner is started. and
WTR timer running signal is
continuously generated. When the
WTR timer expires and no switching
request of a higher priority is
received, a WTR expire signal is
continuously generated.
To adjust the switching sequence between the ERPS and
other coexisting protection schemes. The holdoff timer
allows a fault that triggers another protection
switching (for example, the LAG protection) to be rectified
before ERPS switching. When the ring node detects one
or more new faults, the holdoff timer is started. When the
holdoff timer is running, the fault is not reported to the
ERPS scheme for processing. When the holdoff timer
expires, the link status is checked regardless of whether
the fault that starts the timer persists. If the fault persists,
the fault is
reported to the ERPS scheme for protection switching.
The reported fault may not be the same as the fault that
starts the holdoff timer.
100 ms steps between 0s and 10s with an accuracy
of 5 ms. The default value is 0s.
Switching Condition
Local SF When a ring node detects the local SF condition on one of its ring ports, the ring node blocks the service channel
and R-ASP channel of this ring port.
In this case, the two ring ports on this ring node transmit the R-APS (SF) message.
The local SF condition enables the ring node to empty the MAC address table.
SF switching is triggered when any of the following alarms is reported: hardware fault on the IF board or the
IF unit, hardware fault on the ODU, VOLT_LOS (on the IF board), RADIO_TSL_HIGH, RADIO_TSL_LOW,
RADIO_RSL_HIGH, RADIO_RSL_HIGH, R_LOC, R_LOF, MW_LOF, MW_BER_EXC, BIP_EXC, and
MW_FECUNCOR - ETH_LOS or ETH_LINK_DOWN

Reception of
the R-APS(SF)
- When an RPL owner receives the R-APS (SF) message and does not receive a local switching request of a
higher priority, the RPL owner unblocks the RPL connection point that is already blocked and thus connects the
service channel on the RPL.
- When an RPL owner receives the R-APS (SF) message and the local SF condition persists, the RPL owner
ignores the R-APS (SF) message.
- When the other ring nodes receive the R-APS (SF) message that does not contain the DNF flag, these ring
nodes empty their MAC address tables.
- When the other ring nodes receive the R-APS (SF) message that contains the DNF flag, these ring nodes do
not empty their MAC address tables.
WTR timer
Expired
>> When a ring node detects that the local SF condition on another ring node is cleared, this ring node continuously
transmits the R-APS (NR) message, through its two ring ports, to the Ethernet ring to inform that no switching
request exists at the local end. In addition, this ring node starts the guard timer.
>> On the reception of the R-APS (NR) message, the RPL owner starts the WTR timer. During the duration period of
the WTR timer, the reception of the R-APS (SF) message or the generation of the local SF condition at the RPL
owner stops the WTR timer.
>> When the WTR timer expires and a trigger condition of a higher priority does not exist, the RPL owner blocks the
service channel on the RPL and then transmits the R-APS (NR, RB) message, through its two ring ports, to the
Ethernet ring to inform that the RPL is blocked. In addition, the RPL owner empties the MAC address table.
Q- in case of DNF =0 , does the static entries in MAC Table erased ??
Reception of
the R-APS (NR, RB)
>> When the other ring nodes receive the R-APS (NR, RB) message that does not contain the DNF flag, all
the ring nodes on which the local SF condition does not exist unblock all the non-RPLs that are blocked and
empty their MAC address tables.
>> If the R-APS (NR, RB) message is received after all the preceding actions are performed, the ring node
no longer empties its MAC address table.
Switching Impact (less than 100 ms).
Availability EM6T , EM6F , IFU2 , IFX
The ERPS is associated with the 1+1 protection, LAG, and SNCP.
* The 1+1 Hybrid radio link can function as the ring link or ring protection link in the ERPS protection.
* The FE/GE link in the LAG or the 1+1 Hybrid radio link can function as the ring link or ring protection link in the ERPS protection.
* The Hybrid microwave ring can use the SNCP and ERPS to respectively protect the E1 services and Ethernet services on the ring.
Relation with Other Features
Realization Principle
Scenario 2
Scenario 1
(in the case of a fault on a non-RPL link) (in the case of a fault on an-RPL link)
3. NE A and NE B detect the local SF condition.
After the holdoff timer expires, NE A and
NE B block the ports that are connected to the
faulty link and empty the MAC address table.

4. NE A and NE B keep transmitting the R-APS
(SF) message to the Ethernet ring periodically
when the SF condition persists.
5. The ring nodes that receive the R-APS (SF)
message empty their MAC address tables.
When the RPL owner receives the R-APS (SF)
message, it unblocks the blocked RPL connection
point.

6. The ERPS is complete and the ring becomes
stable.
8. NE A and NE B detect that the SF condition is
cleared. In this case, NE A and NE B start
the guard timer and start to periodically transmit
the R-APS (NR) message the other ring nodes.
9. When the RPL owner receives the R-APS
(NR) message, it starts the WTR timer. After
the WTR timer expires, the RPL owner blocks
the RPL connection point. In addition, the
RPL owner starts to transmit the R-APS (NR,
RB) message and empties the MAC address
table.
10. When NE A and NE B receive the R-APS (NR, RB) message, they unblock the blocked ring ports and stop transmitting
the R-APS (NR) message. In addition, NE A, NE B, and NE C empty their MAC address tables.
Scenario 2
Can you guess the realization
Principle in that case. ?
Relevant Alarms
MULTI_RPL_OWNER
The MULTI_RPL_OWNER indicates that
more than one RPL owner node exists on
the Ethernet ring network.
Root causes of ERPS failure
1- Hold-Off Time(ms) is set to a value longer
than the permitted delay time.

2- Two or more Ethernet links on the Ethernet
ring network are faulty [The ERPS provides
protection only against one link failure.]

3- Control VLAN is the same as service or
Inband DCN VLAN.

4- ERPS parameters are not set to the same
values for each node

5- Different ERPS protection instances use
one or more same ring ports.

6- More than one RPL owner node is
configured on the Ethernet ring network.

Appendix B [ MSTP ]
Thank you
www.huawei.com

4 - Ethernet Service

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

4 - Ethernet Service

Uploaded by

Copyright:

Available Formats

www.huawei.

You might also like