OptiX RTN 900 V001R002 Ethernet Service Planning and Design Guide-20100114-A

8/11/2019 OptiX RTN 900 V001R002 Ethernet Service Planning and Design Guide-20100114-A

1/56

HUAWEI TECHNOLOGIES CO., LTD.

www.huawei.com

Huawei Confidential

Security Level:2014/9/22

OptiX RTN 900 V001R002

Ethernet Service Planning

and Design Guide

Network Product Service Dept.


2/56

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

Introduction

This course is developed for

planning and designing Ethernet

services on the OptiX RTN 900

V001R002.

With the guidance of this course,

you can separately plan and

design common Ethernet services

on the OptiX RTN 900 V001R002.


3/56


Guidelines for Learning This Course

This course provides information about planning and

designing Ethernet services on the OptiX RTN 900

V100R002 (Hybrid radio).

Before starting this course, it is recommended that

you learn about the Principles of Ethernet Network

and the Ethernet Service and Networking Application

of the OptiX RTN 900 V100R002.

The key points of this course are the principles for

and methods of planning and designing common

Ethernet services on the OptiX RTN 900 V100R002.


4/56


Objectives

After completing this course, you can:

Master the principles for planning Ethernet

services in the case of Hybrid radio.

Master the methods for designing Ethernet


Separately plan and design Ethernet



5/56


Contents

Selecting Ethernet Boards

Planning Services and Networking Modes

Setting the Port Parameters for Ethernet

Boards

Planning the QoS Policies

Planning the Protection Schemes for

Ethernet Ports

Examples


6/56


Selecting Ethernet Boards Generally, the user-network interface (UNI) on the access-layer

equipment is connected to a base station. In the case of an Ethernet

service, an FE port is connected to a base station. In the case of the

OptiX RTN 950 equipment, you can select the EM6T board (a 6xFE

electrical interface board) or the EM6F board (a board with four FE ports

and two GE ports), depending on the interface type at the opposite basestation. In the case of the OptiX RTN 910 equipment, the Ethernet port on

the CSHA, CSHB, or CSHC board is required.

The access-layer equipment needs to transmit the signals from a base

station over radio links. Therefore, the IFX2 or IFU2 board (an IF board)provides the UNI port. Each IFX1 or IFU2 board provides a radio link.


7/56


Contents Selecting Ethernet Boards



Boards



Ethernet Ports

Examples


8/56


Contents


Service Types

Planning the Service Types

Planning the VLANs

Planning the Service Bandwidth


9/56


Ethernet Services Supported by the OptiX

RTN 900

The OptiX RTN 900 V100R002 equipment supports E-Line services (Ethernet

private line services) and E-LAN services (Ethernet private network services).

An E-Line service is a point-to-point (P2P) service. The equipment transmits the

packets from a specified port or a specific VLAN of the specified port on the user

side to a port on the user or network side, therefore achieving the P2P transparent

transmission of the user data. E-Line services are classified into EPL and EVPL

services that are specified by ITU-T.

An E-LAN service refers to dynamic transmission of a multipoint-to-multipoint

(MP2MP) Ethernet service based on the MAC address table. E-LAN services include

the EPLAN and EVPLAN services specified by ITU-T. The core factor of an E-LAN

service is a bridge. By using the self-learning function, the bridge can create an

Ethernet port and gain access to the mapping relationships between the Ethernet

ports and the source MAC sources in the Ethernet frames that enter the bridge. Themapping relationships form a MAC address table.

You can select different service types according to the service scenario and

situation.


10/56


Introduction to E-Line Services E-Line services are classified into P2P transparently transmitted E-Line services, VLAN-based E-Line

services, and QinQ-based E-Line services. The following table lists the specific service models.

Service Type Encapsulation

Type at the Port

Service

Direction

Service Flow Service Description

P2P transparently

transmitted E-Line

Services

Null (source)

Null (sink)

UNI to UNI PORT (source)

PORT (sink)

The source port transparently transmits all the received Ethernet frames to

the sink port.

VLAN-based E-Line

services

802.1Q (source)

802.1Q (sink)

UNI to UNI PORT (source)

PORT (sink)

The source port processes the received Ethernet frames according to the

TAG attributes and then transmits the Ethernet frames to the sink port.

The sink port processes the received Ethernet frames according to the TAGattributes and then transmits the Ethernet frames.

PORT+VLAN

(source)

PORT+VLAN (sink)

The source port processes the received Ethernet frames according to the

TAG attributes and then transmits the Ethernet frames that contain the

specified VLAN ID to the sink port.

The sink port processes the received Ethernet frames according to the TAG

attributes and then transmits the Ethernet frames.

QinQ-based E-Line

services

Null (source)

QinQ (sink)

UNI to NNI PORT (source)

QinQ link (sink)

The source port adds the S-VLAN ID that corresponds to the QinQ link to all

the received Ethernet frames, and then transmits the Ethernet frames to the

sink port of the QinQ link.

802.1Q (source)QinQ (sink)

UNI to NNI PORT (source)QinQ link (sink)

The source port gains access to only the Ethernet frames that contain VLANtags. After adding the S-VLAN ID of the QinQ link to the Ethernet frames, the

source port transmits the Ethernet frames to the sink port of the QinQ link.

PORT+CVLAN

(source)QinQ link (sink)

The source port adds the S-VLAN ID of the QinQ link to the received

Ethernet frames that contain the specified C-VLAN IDs, and then transmitsthe Ethernet frames to the sink port of the QinQ link.

QinQ (source)

QinQ (sink)

NNI to NNI QinQ link (source)

QinQ link (sink)

The source port transmits the Ethernet frames that contain the specified S-

VLAN IDs, and then transmits the Ethernet frames that contain the S-VLAN

IDs of the source QinQ link to the sink port of the sink QinQ link.

If the corresponding S-VLAN IDs of the source and sink QinQ links are

different from each other, the S-VLAN IDs in the packets are exchanged.


11/56


Introduction to E-LAN Services E-LAN services have three types of bridges: 802.1d bridge, 802.1q bridge, and 802.1ad bridge.

Item 802.1d Bridge 802.1q Bridge 802.1ad Bridge

Type of the logical port PORT PORT+VLANPORT or PORT+CVLAN (UNI port)

PORT+S-VLAN (NNI port)

Tag type Tag-Transparent C-Awared S-Awared

Encapsulation type at

the port

Null Null or 802.1Q Null or 802.1Q (UNI port)

QinQ (NNI port)

Type of the logical port PORT PORT+VLAN PORT (the encapsulation type of the UNI is Null)PORT or PORT+CVLAN (the encapsulation type of the

UNI is 802.1Q)

PORT+SVLAN (NNI port)

Learning mode SVL IVL IVL

Broadcast domain The entire bridge All the logical ports with the same

VLAN ID

All the logical ports with the same S-VLAN ID

Sub-switching domain Not divided into sub-

switching domains

Divided into sub-switching domains

based on the VLAN ID

Divided into sub-switching domains based on the

S-VLAN ID

The core factor of an E-LAN service is a bridge. By using the self-learning function, the bridge can create thecorresponding relationships between the Ethernet ports and the source MAC addresses in the Ethernet frames that

enter the bridge. The learning modes of a bridge are classified as follows:

Shared VLAN learning (SVL): A table entry is created in the MAC address table according to the source MAC

address and source port of the port. The table entry is valid for all the VLANs.

Shared VLAN learning (IVL): A table entry is created in the MAC address table according to the source MAC

address, VLAN ID, and source port of the packet. The table entry is valid for the VLAN only.


12/56


Contents


Service Types

Planning Service Types

Planning the VLANs



13/56



In the case of access services at a base station, you can select the E-Line service that is

transmitted in transparent and P2P mode. In the case of the OptiX RTN 910 equipment, the

Ethernet service port on the CSHA, CSHB, or CSHC board is used to gain access to data

services. In the case of the OptiX RTN 950 equipment, the EM6T board is used to gain access

to data services.

In the case of service convergence on a convergence node, VLAN-based E-Line services or E-

LAN services are required. If Ethernet services on a ring need to be protected, E-LAN services

are required. If a scenario requires layer-2 switching (for example, P2P service convergence, and the base

stations with the same VLAN ID) and E-LAN services, you need to plan the relevant bridges.

When planning the bridges, adhere to the following principles:

The 802.1q bridge is preferred in the case of EVPLAN services. If the VLANs of the

customer are unknown and the customer does not intend to isolate the data between

different VLANs, you can use the 802.1d bridge in the case of EPLAN services.

If layer-2 switching services are converged from multiple tributary nodes to a convergencenode, set the convergence node to the Hub attribute, and then set the tributary nodes to

the Spoke attribute. In the case of multipoint-to-multipoint (MP2MP) layer-2 switching

services, set the convergence node to the Hub attribute.


14/56


Selecting Service Types

NE1

NE3

NE2

NE4

RNC

NodeBNodeB

NodeB

If the service VLANs at the

following base stations are different

from each other, select the VLAN-

based E-Line services.

You can distinguish the services at

different base stations from each

other according to the VLAN ID.

Transparently

transmitted E-Line

services required

If partial VLAN IDs of the services at the base

stations are the same, select the E-LAN

service, and converge the services based on

layer-2 switching. If the VLAN information is

available, it is recommended that you use the

802.1q bridge.

Transparently

transmitted E-Line

services required

Transparently

transmitted E-Line

services required


15/56



BSC/RNC #1

Application Scenario 1 of

2G/3G Services

BSC/RNC #2

FE: No VLAN

MAC1

MAC2/3

MAC1/2/3

MAC2

MAC3

MAC2/3

FE: VLAN1

FE: No VLAN

BTS/NodeB MAC1

BTS/NodeB MAC2

BTS/NodeB MAC3

Scenario requirements:

(1) PMP service applications

(2) Microwave transmission is not

sensitive to VLAN planning of a

base station, and services need to

be converged.

Scenario description:

(1) Gain access to and converge one

box.

(2) Converge the services based on

MAC address exchange, and

perform statistical multiplexing of

network-level bandwidth.

(3) Add base stations and rehoming,and do not update the transmission

configuration.

(4) Perform self-learning of MAC

addresses, and automatically

create service forwarding paths.

Rehoming from BSC/RNC 1

to BSC/RNC 2 without

updating the transmission

configuration


16/56


E-LAN1 (Area 1)

E-LAN2 (Area 2)


BTS/NodeB MAC4

FE: No VLAN

Application Scenario 2

of 2G/3G Services

BTS/NodeB MAC3

BTS/NodeB MAC2

BTS/NodeB MAC1

FE: VLAN2

FE: VLAN1

FE: VLAN1

BSC/RNC MAC4

BSC/RNC MAC5


(1) The VLANs of the base

stations are planned by

area, and the microwave

services need to be

converged.

(2) The services between

different areas need to be

isolated from each other.

Adding VLAN 2


(1) Gain access to and converge one box.

(2) Converge the services based on MAC address and VLAN switching,

and perform statistical multiplexing of network-level bandwidth.

(3) VLANs are used to isolated the services in different areas, therefore

narrowing down the broadcast domains.

(4) When more base stations are added or the base stations are rehomed

in an area, the configuration on the transmission side are not changed.

When the base stations are rehomed between areas, only the VLAN

IDs need to be changed.(5) Perform self-learning of MAC addresses, and automatically create

service forwarding paths.

MAC1

MAC2

MAC1/2MAC1/2

MAC3/4

MAC1/2/3/4VLAN

1

VLAN

2

MAC3

MAC4

MAC3/4


17/56



BSC/RNC/AGW/aGW

No service interaction between 2G/3G base stations, and the entire backhaul

network is of a tree topology.

When E-LAN services are deployed on the central node, the following

problems occur:

(1) Information security cannot be ensured, because any two nodes can

communicate with each other.

(2) The upstream broadcast packets at the base stations are diffused to the other

base stations.

Background of introducing horizontally split groups

Application Scenario


(1) At least member port in the E-LAN service is a port in a non-splitgroup. The port connected to the base station and does directly

communicate with the base station is a member port in a split group.

(2) The service model is E-LAN.


(1) The members in a split group cannot directly

communicate with each other. The members in a

non-split group can communicate with each other,and the members in a non-split group can

communicate with the members in a split group.

(2) The members in a split group can communicate

with each other based on the forwarding performed

by the non-split group.

Horizontally-split group

Non-split

group


18/56


Contents


Service Types


Planning the VLANs



19/56


Planning the VLANs The VLANs of microwave Ethernet services are set according to the VLANs

planned for wireless base stations. Therefore, you need to obtain the VLAN

planning documents for wireless base stations before planning VLANs for

microwave Ethernet services.

In the case of transparently transmitted P2P E-Line services and the 802.1d

bridge based E-LAN services, no operations are required for the VLANs.

In the case of other services, adhere to the following principles:

If the VLAN IDs of the base stations are different from each other, VLAN-based E-Line

services are required. The VLAN IDs of the services at the corresponding base stations

are required for the ports that are connected to the access sites.

If all or partial VLAN IDs are used to gain access to the base stations are the same, E-LAN

services are required. If the 802.1q bridge is used, you need to specify the ports and aggregation ports whose VLAN IDs

are the same in the VLAN filter table. The number of VLANs determines the number of VLAN filter

tables. If the 802.1d bridge is used, you do not need to divide the VLAN filter table. You need, however, set

the Hub and Spoke attributes of the ports (Set the aggregation port to Hub, and set the VCTRUNK

and aggregation ports to Spoke, that is, perform operations on the horizontally-split group).


20/56


Planning the VLANs

Convergence

Access

NodeB/BTS NodeB/BTS NodeB/BTS NodeB/BTS

RNC/BSC

The VLAN IDs of the access nodes

are different from each other,

respectively VLAN1, VLAN2, VLAN3,

and VLAN4.

In the case of convergence nodes, the

VLAN-based E-Line services are

required. Each access node requires

one E-Line service whose VLAN ID is

the VLAN ID of the corresponding

access node.

The access node uses the transparently

transmitted E-Line services without

performing operations on the VLAN.

Therefore, no VLAN planning is required.

VLAN1Port 1 - port3

VLAN1 VLAN2 VLAN3 VLAN4

VLAN2

Port 2 - port3

VLAN3

Port 1 - port3

VLAN4

Port 2 - port3

VLAN1, 2

Port 1 - port5

VLAN3, 4

Port 2 - port5


21/56


Planning the VLANs

Convergence

Access

NodeB/BTS NodeB/BTS NodeB/BTS NodeB/BTS

RNC/BSCAll or partial VLAN IDs of the access

nodes are the same.

The convergence node converges the

services through LAN and layer 2

switching.

If the 802.1q bridge is used, you need toadd a VLAN filter table.

If the 802.1d bridge is used, you need not

add a VLAN filter table.

Set the convergence port to the Hub

attribute, and set other ports to the Spoke

attribute.

The access node uses the E-Line service,which performs transparent transmission

and does not process the VLAN ID,

therefore not requiring the VLAN planning

or configuration.

VLAN1 VLAN1 VLAN1 VLAN1

802.1d bridge

VB1 covers port 1, port 2, and

port 3.

Port 3 is set to the Hub attribute.

Port 1 and port 2 are set to the

Spoke attribute.

802.1q bridge

VB1 covers port 1, port 2,

and port 3.

VLAN1 filter table: port 1,

port 2, and port 3.


22/56


Contents

Planning Services and Networking

Modes

Service Types


Planning the VLANs



23/56



The Hybrid radio transmits the Native Ethernet services. The bandwidth

of the port need not be planned and is only required to match the

bandwidth of the customer-side interface.

If the hybrid radio equipment functions as a base station, transparent

transmission is required. The uplink bandwidth of the Ethernet board is

determined by the peak bandwidth of the base station.

In the case of a convergence node, the uplink bandwidth of the Ethernet

board is determined according to the "convergence algorithm", which is

currently not confirmed. Therefore, the uplink bandwidth of the Ethernet

board is calculated according to the total downlink bandwidth.


24/56


Contents

Selecting Ethernet Boards


Setting the Port Parameters Planning the QoS Policies


Ethernet Ports

Examples


25/56


Introduction to the Ports

Two types of Ethernet ports are available for the OptiX RTN 900 V100R002. One is theFE/GE port on the Ethernet interface board, and the other one is the IF_ETH port.

IF_ETH port:

If Ethernet services need to be transmitted over Hybrid radio, you need to configure the

Ethernet services between the FE/GE port on the Ethernet interface board and the IF_ETH

port on the Hybrid IF board.

The IF_ETH port is an internal Ethernet port on the Hybrid IF board. In the case of Hybrid

radio, 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 in the

reverse direction, 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 port that receives or transmits MAC frames and does not

provide physical-layerfunctions.

The bandwidth on the IF_ETH port is equal to the Ethernet service bandwidth that the

Hybrid radio supports. Hence, when the AM function is enabled in the case of Hybrid radio,

the bandwidth on the IF_ETH port changes according to the modulation scheme.


26/56


Setting the Port Parameters

Enable port:By default, this parameter is set to "Disable". If a port needs to be used, set this parameter to

"Enable". Otherwise, set this parameter to "Disable".

Encapsulation type:This parameter specifies the method of the port to process the received packets. If this

parameter is set to Null, the port transparently transmits the received packets. If this parameter is set to 802.1Q,

the port identifies the packets that comply with the IEEE 802.1Q standard. If this parameter is set to QinQ, the

port identifies the packets that comply with the IEEE 802.1 QinQ standard.

In the case of P2P E-Line services and 802.1d-based E-LAN services, set this parameter to "Null".

In the case of VLAN-based E-Line services and 802.1q-based E-LAN services, set this parameter to

"802.1q".

In the case of QinQ E-Line services and 802.1ad-based E-LAN services, set this parameter to NULL if

the UNI-side port allows the access of untagged frames, and set this parameter to "802.1q" if the UNI-side

port allows the access of only tagged frames. set this parameter to "QinQ" in the case of NNI-side port.

Working mode:This parameter is set to auto-negotiation by default. The working modes of the ports on the

interconnected equipment must be the same. If the OptiX RTN equipment is interconnected with each other, it

is recommended that you set this parameter to the default value (namely, auto-negotiation). If an Ethernet port

is connected to the external equipment, its working mode must be set to the same as the working mode of the

port on the opposite equipment (generally, the port on the external equipment works in auto-negotiation mode).If Ethernet ports at both ends are located within a network, their working modes are set to "auto-negotiation".

Maximum transmission unit (MTU):Generally, this parameter is set to the default value 1522", which needs

to be changed if necessary. When jumbo frames are transmitted, set the value of this parameter according to

the actual length of the jumbo frames. Otherwise, it is recommended that you set the value of this parameter to

1536.


27/56


Setting the Port Parameters Traffic control:When the traffic control function is enabled, the Ethernet port informs the opposite port of

stopping the transmission of Ethernet packets for a certain period of time by transmitting the PAUSE frames inthe case of link congestion. If the traffic control function is enabled for the external equipment that is connected

to the Ethernet port, the traffic control function must be enabled for the OptiX RTN 900 equipment accordingly.

In this case, set the key parameters as follows:

If the external equipment works in non-autonegotiation traffic control mode, set "Non-autonegotiation

traffic control mode" to "Enable symmetric traffic control".

If the external equipment works in autonegotiation traffic control mode, set Autonegotiation traffic

control mode" to "Enable symmetric traffic control".

TAG identifier:Set this parameter according to the fact whether the received packet contain a VLAN tag. If all

the accessed frames contain VLAN tags (namely, tagged frames), set this parameter to "Tag Aware". If all theaccessed frames do not contain VLAN tags (namely, untagged frames), set this parameter to "Access". If the

accessed services contain tagged frames and untagged frames, set this parameter to "Hybrid". If the QinQ

technology is adopted, this parameter need not be set.

Default VLAN ID and VLAN priority:These two parameters are set only when the tag identifier is set to

Access or Hybrid, indicating that the default VLAN ID and VLAN priority are applied to the access service that

does not carry the VLAN ID.

QinQ type domain:This parameter can be set when "Encapsulation type" is set to "QinQ" on the "Basic

Attributes" tab. The default value of this parameter is "88A8". This parameter cannot be set and its value is

always displayed as "FFFF" when "Encapsulation type" is set to "Null" or "802.1q" on the "Basic Attributes"

tab. If an NNI port is connected to the external equipment, set this parameter according to the T-PID of the

SVLAN that is supported by the external equipment. In the case of the NNI ports on the same network, set this

parameter to the default value. The value of this parameter must be the same for all the ports on the same

EM6T/EM6F board.


28/56


Setting the Port Parameters The advanced attributes of an Ethernet port are used for setting the MAC/PHY loopback and

querying the rate on the port. These advanced attributes are required when you need to enable

the port self-loop test and automatic loopback shutdown functions or to enable the broadcast

packet suppression function.

MAC/PHY loopback:This function is disabled by default, and is enabled only in the case

of fault locating.

Broadcast packet suppression:This parameter limits the traffic of broadcast packetsbased on the proportion of the broadcast packets to the total packets. When a broadcast

storm may occur in the equipment at the opposite end, set this parameter to "Enabled".

Broadcast packet suppression threshold:The received broadcast packets are

discarded if the proportion of the broadcast packets to the total packets exceeds the

specified value of this parameter. Set this parameter to a value that is greater than the

proportion in cases wherein no broadcast storm occurs. Generally, set this parameter to30% or a greater value.

R l f S tti th T Att ib t f


29/56


Rules for Setting the Tag Attributes of

Ethernet Ports

Tag Untag

Tag aware (ingress) The packets are transmitted transparently. The packets are discarded.

Tag aware (egress) The packets are transmitted transparently. -

Access (ingress) The packets are discarded. The default VLAN tag is added.

Access (egress) The VLAN tags are stripped off from the

packets.

-

Hybrid (ingress) The packets are transmitted transparently. The default VLAN tag is added.Hybrid (egress) If the VLAN tags of the packets are the

same as the default VLAN tag of the

packets on the port, the VLAN tags of the

packets are stripped off and then the

packets are transmitted. Otherwise, the

packets are transmitted transparently.

-

Port Attribute

Data

The preceding rules are applicable to VLAN-based E-Line services and 802.1q-based E-LAN services. The VLAN IDs of the packets are

not detected in the case of the 802.1d bridge.

The port attribute is valid only when it is set to UNI (namely, the default value).

The port that receives VLAN-tagged packets is set to "TAG", the port that receives the VLAN-untagged packets is set to "Access", and the

port that receives both VLAN-tagged and VLAN-untagged packets is set to "Hybrid".


30/56




Designing the Port Parameters for

Ethernet Boards



Ethernet Ports

Examples


31/56


Introduction to QoS

Quality of service (QoS) is used for providing services of differentiated quality for the scenarios inwhich different requirements are proposed. For example, real-time services (such as voice services)

are of higher priorities (highest availability), and data services (such as Internet access services)

are non-real-time services and have lower priorities (lower availability).

The following figure illustrates how QoS is implemented on packet transmission through priority

queuing (PQ).

Classification

High

Medium

Low

Outgoing scheduling

Packets transmitted from the portPackets to be

transmitted by this port

Normal

Queue

Urgent packets

Non-urgent packets

Secondary-urgent packets

Note:


32/56


Introduction to QoS

In microwave transmission, Ethernet services need to adapt to the change of transmission

bandwidth, which is adjusted adaptively based on theAM technology. This means that different

services need to be differentiated by QoS and the services of higher priorities must be protected

against packet loss. Therefore, the AM technology of Hybrid radio is closely associated with the

QoS implementation of Ethernet services.

With the support of excellent QoS performance, high-quality microwave transmission can be

ensured for real-time and higher-priority services (such as voice and IPTV services). In addition,

in the case of bad weather, packet loss is allowed to occur in other lower-priority services (such

as Internet access services) when bandwidth changes due to the adjustment of the microwave

modulation mode.


33/56


QoS Features of the OptiX RTN 900 V100R002

Board Item Description

CSHA/CSHB/

CSHC,

EM6F/EM6T,

IFU2/IFX2

Traffic

classification

Supports traffic classification based on port, C-VLAN ID, S-VLAN ID, and traffic

classification for the C-VLAN/S-VLAN packets based on the 802.1p priority and

DSCP.

Traffic policing Supports the setting of CAR, PIR, and CIR in the increments of 64 kbit/s.

Queue

scheduling

Supports scheduling of eight classes of priority queues on each Ethernet port.

Supports the setting of the queue scheduling mode of each Ethernet port to SP,

SP+WRR, or WRR, according to the actual requirement.

Traffic shaping Supports the traffic shaping over a specified port, higher-priority queues or service

flow, and supports the setting of PIR and CIR in the increments of 64 kbit/s.

Buffer capacity 12 Mbit


34/56



Simple traffic classification

Classification technologies: C-VLAN priority, S-VLAN priority, and DSCP

Different flows can be mapped into different queues according to the mapping table in the

ingress direction.

The values of C-VLAN priority, S-VLAN priority, and DSCP of the packets in different queues

can be changed according to the mapping table in the egress direction.

The OptiX RTN 900 V100R002 does not support coloring. Only eight queues are available

on the equipment. AF1x belongs to the AF1 queue (x = 1, 2, 3). It is similar in the case of

other AF queues.

Complex traffic classification

Classification technologies: C-VLAN ID, S-VLAN ID, C-VLAN priority, S-VLAN priority, DSCP,

C-VLAN ID + C-VLAN priority, and S-VLAN ID + S-VLAN priority.

Traffic-associated operations:

ACL: discards or forwards the traffic.

CAR: manages the traffic in the ingress direction and changes the forwarding queues of

the packets marked yellow (only the packet marked yellow are supported)

Shaping: performs shaping on the traffic in the egress direction.


35/56



Managing CoS queues

Each port has eight queues.

The supported queue scheduling algorithms are as follows:

SP queues

WRR queues

SP+WRR: certain SP queues and certain WRR queues (the WRR queues must be

consecutive)

Queue shaping: supports the rate limit of each queue in the egress direction.

Default forwarding priorities: CS7, CS6, EF, AF4, AF3, AF2, AF1, and BE.

CS6 - CS7: indicates the highest service class that is adopted for signaling transmission.

EF: indicates fast forwarding that is applicable to the services (such as voice services) of low

delay and low packet loss rate.

AF1-AF4: indicates assured forwarding that is applicable to the services that require assuredrate but do not have restrictions on delay or jitter.

BE: applicable to the services that do not require special operations. It can be set for the

ingress direction.

The default priority is BE.


36/56


QoS Planning Guidelines Select the proper QoS function as required. When selecting the QoS function, adhere to the following

principles: The CAR is preferred if the traffic at the ingress port needs to be controlled.

If an important service requires the improvement in traffic fluctuation, select the traffic shaping function

(shaping for rate limit at the egress port).

If differentiated services are required for different service types or different user classes, select the CoS

function.

When planning the CAR, adhere to the following principles:

The sum of CAR and CIR for all the traffic associated with a port cannot exceed the physical bandwidth of

the port.

When planning the traffic shaping and CoS, adhere to the following principles:

Allocate the services of low delay or the services of low delay commitment (such as the signaling data,

VoIP data, and network management protocol packet) to the queues of strict priority.

Schedule the services that do not require low delay or that do not have low-delay commitment (such as

the Internet service) to the WRR queue.

The sum of CIRs for all the traffic associated with a port cannot exceed the physical bandwidth of the port

and the rate limit bandwidth of the egress port.

Set the parameters of traffic shaping according to the traffic features, thus preventing frequent buffer

overflow.

Precautions for IF ports:

The physical bandwidth of an IF port is determined by many factors. When configuring the QoS of an IF

port, consider the actual bandwidth of the IF port.


37/56


QoS Planning Guidelines

When the AM function is enabled, it is recommended that you configure the QoS for Ethernetservices transmitted over the Hybrid radio. After the QoS is configured, available bandwidths

are first allocated to transmit Ethernet services of higher priorities when the radio link works in

low-order modulation mode.

When planning the QoS function, adhere to the following principles:

Determine the traffic classification of the service. That is, determine the method of

distinguishing the services of different priorities (for example, by port or by VLAN), andadopt the corresponding traffic classification. All the QoS policies are based on traffic.

Bind the traffic of different priorities to the corresponding CoS. Schedule the Ethernet

services of higher priorities to the high-priority queues, and schedule the Ethernet services

of lower priorities to the low-priority queues.

Enable the CAR function for the QoS-supporting Ethernet service ports that gain access to

the Ethernet services. Therefore, you can prevent the traffic that enters these ports from

exceeding the maximum traffic allocated to the Ethernet services by Hybrid radio.

Apply traffic shaping to the ports that have unstable traffic, therefore balancing the traffic at

these ports.


38/56


QoS Planning Guidelines

DS domain: A default DiffServ (DS) domain is available for the OptiX RTN 900 equipment. Its "Mapping

relationship ID" is 1, and its "Mapping relationship name" is "Default Map". If these parameters are not set, all

the ports belong to the domain. The default DS domain cannot be modified or deleted. The default DS domainis mapped according to the C-VLAN priority. The PTP transparent transmission services support only the

DSCP mapping of the PHB service class. Therefore, in the case of transparently transmitted PTP E-Line

services and 802.1d-based E-LAN services, you need to plan the DS domain according to the requirements. In

the case of other services, it is recommended that you use the default DS domain, if possible.

PHB: When service packets are mapped to PHB service levels, do not use the CS7 queue if possible. This is

because that an NE may use the CS7 queue to transmit Ethernet protocol packets or inband DCN packets.

Queue scheduling: Generally, all the Ethernet ports of a service adopt the same queue scheduling method.

CAR and shaping: If CAR or shaping is required for a specified service, generally, configure the correspondinginformation at the edge node of the DS domain.

If the Ethernet bandwidth planned for the aggregation link is lower than the total bandwidth of the

aggregation services, perform port shaping at the edge node to limit the Ethernet service traffic that

travels to the aggregation node, therefore preventing congestion on the aggregation link. When port

shaping is not configured, the OptiX RTN 900 automatically performs port shaping for the IF_ETH ports.

The GE/FE lease mode is based on bandwidth lease. If the leased bandwidth is less than the bandwidth

for a port, you need to configure the shaping policy to ensure the CoS of the service on the leased

network. In the case of a 2G/3G base station and an RNC, traffic control is required, and the microwave form is

changed. Generally, CAR/shaping (traffic policing) is not required for backhaul transmission.


39/56





Boards



Ethernet Ports

Examples


40/56


Introduction to Ethernet Port Protection

The CSHA, CSHB, CSHC, EM6F, EM6T, IFU2, and IFX2 boards support

protection of LAGs.

A link aggregation group (LAG) allows multiple links that are connected to the same

equipment to be bound together to form a LAG so that the bandwidth increases and the

reliability of the links is improved. An LAG can be regarded as a logical link. As shown in

the following figure, there are three 100 Mbit/s links between the two pieces of equipment.

By implementing LAG, the three links are bound to be one 300 Mbit/s logical link.


41/56


Introduction to Ethernet Port Protection

A LAG supports the following aggregation types:

Manual aggregation

A user manually creates a LAG. To add or delete a member port, the user need not

start the link aggregation control protocol (LACP).

Static aggregation

A user creates the LAG manually. To add or delete a member port, the user needs to

start the LACP.

A LAG supports the following load sharing modes: Load sharing

Each member link in a LAG carries traffic. That is, the member links in the LAG share

the load.

Non-load sharing

In a LAG, only one member link carries traffic, and the other member links are in

standby state. In this case, a hot backup mechanism is provided.


42/56



Ethernet Ports

Determining the members of a LAG (number of ports, master and slave ports) Determine the members of a LAG according to the number of interconnected ports and the required

bandwidth. For example, if two ports are interconnected with the port on the opposite equipment, the LAG

needs to have two ports accordingly. The master port is interconnected to the master port on the opposite

equipment.

A LAG can have one master port only. The main port represents a LAG to participate in service configuration.

the master port must always belong to the LAG untilthe LAG is deleted.

In a LAG, the other ports are slave ports, except the master port. A LAG can have several slave ports. Aslave port cannot participate in service configuration.

LAG type

Determine the LAG type based on the requirement of the opposite equipment, and ensure that the LAG types

of the interconnected equipment are the same. If the opposite equipment is in static aggregation state, you

need to set the local equipment to the static aggregation state (namely, running the LCAP). If the opposite

equipment is in manual aggregation state, you need to set the local equipment to the manual aggregation

state. Load sharing mode

Determine the load sharing mode based on the requirement of the opposite equipment, and ensure that the

load sharing modes of the interconnected equipment are the same. If the opposite equipment is in load

sharing mode, you need to set the local LAG to the load sharing mode. If the opposite equipment is in non-

load sharing mode, you need to set the local equipment to the non-load sharing mode.



43/56



Ethernet Ports Port priority

The port priority is valid for static aggregation only. This parameter 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.

Determine the port priority based on the requirements of the interconnected equipment and services. Generally,

the master port is of the highest priority.

System priority

The system priority is valid for static aggregation only. This parameter indicates the priorities of the ports in a

LAG. The smaller the value, the higher the priority. If the local LAG and the opposite LAG negotiate with each

other for the system priority through the LACP, the higher priority prevails for both LAGs. If the priorities of both

LAGs are the same, the system MAC addresses are compared. Then, the comparison result based on the LAG

with smaller system MAC address is considered as the result of both LAGs and is used to ensure that the

aggregation information is consistent at both LAGs.

Determine the system priority based on the requirement of the opposite equipment. If the customer requires the

operation result of the LACP on the customer-side equipment, the system priority of the local LAG needs to be

set to the priority lower than the priority of the opposite LAG. Otherwise, the system priority of the local LAG

needs to be set to the priority higher than the priority of the opposite LAG. Generally, set the system priority tothe default value (either one functions as the main equipment).


44/56





Boards



Ethernet Ports

Examples


45/56

Selecting the Equipment Type and Planning


46/56


Selecting the Equipment Type and Planning

Service Types NE1 and NE2 are OptiX RTN 950 NEs. NE1 is connected to the RNC. In this example, an optical port on the RNC is used as the data

port for connecting NE1. Therefore, NE1 uses the EM6F board for connecting the optical port on the RNC. NE2 is connected to

NodeB 1. In this example, an electrical port on NodeB 1 is used as the data port for connecting NE2. Therefore, NE2 uses the EM6Tboard for connecting the electrical port on NodeB 1. NE3, NE4, and NE5 are OptiX RTN 910 NEs, which use the CSHA boards to

access Ethernet services. On the NMS, the logical Ethernet board of the CHSA is 7-EM4T.

VLAN-based E-Line

service VLAN-based E-Line

service

VLAN-based E-Line

service

IEEE 802.1q bridge-based E-

LAN service

Certain VLAN IDs conflict with

each other on this network.

Therefore, E-Line services cannot

be configured on all the NEs. For

example, to achieve service

aggregation, you need to

configure Ethernet services as E-

LAN services on an aggregation

node where certain VLAN IDs

conflict with each other.


47/56


Information About Ethernet Ports

NE5NE4NE3NE2NE1

Tag AwareTag AwareTag AwareTag AwareTag AwareTag AwareTag AwareTag attribute

DisabledDisabledDisabledDisabledDisabledDisabledDisabledFlow control

1536153615361536153615361536Maximum frame

length

Auto-

negotiation

Auto-

negotiation

Auto-

negotiation

Auto-

negotiation

Auto-

negotiation

Auto-

negotiation

Auto-

negotiation

Working mode of

the port

802.1q802.1q802.1q802.1q802.1q802.1q802.1qEncapsulation

type

7-EM4T-17-EM4T-17-EM4T-27-EM4T-11-EM6T-31-EM6F-21-EM6F-1

Parameter

In this example, the GE ports on the RNC and the FE ports on all the NodeBs work in auto-negotiation mode. Therefore, all

the ports on each NE for accessing services also work in auto-negotiation mode. For example, if the peer Ethernet port

changes to another working mode, the local Ethernet port also needs to change to the same working mode accordingly.

In this example, the maximum frame length is planned to be 1536 so that Ethernet frames with more than one layer of tags

(for example, QinQ tags) can traverse the OptiX RTN 900 V100R002 equipment.

Generally, the flow control function is enabled only if the local NE or opposite equipment has insufficient QoS capabilities.

The flow control planning result at the local end must be adjusted adaptively according to the flow control planning result.

In this example, all the services carry VLAN tags. Therefore, the TAG attributes of all the ports are Tag Aware.


48/56


Information About the IF_ETH Port

3-IFU2-14-IFU2-13-IFU2-13-IFU2-16-IFU2-14-IFU2-15-IFU2-13-IFU2-15-IFU2-13-IFU2-1

EnabledEnabledEnabledEnabledEnabledEnabledEnabledEnabledEnabledEnabledErrored frame

monitoring

Tag

Aware

Tag

Aware

Tag

Aware

Tag

Aware

Tag

Aware

Tag

Aware

Tag

Aware

Tag

Aware

Tag

Aware

Tag

AwareTAG attribute

802.1q802.1q802.1q802.1q802.1q802.1q802.1q802.1q802.1q802.1qEncapsulationtype

NE5NE4NE3NE2NE1Parameter

The majority of the backhaul services on the NodeBs are Internet services. Therefore, the errored frame discarding

function needs to be enabled.


49/56


Information About LAGs

To improve service transmission reliability, NE1 and the RNC are interconnected through two LAGs

comprised of GE ports. The planning information about the two LAGs is shown as in the following table.

1-EM6F-2Slave port

1-EM6F-1Main port

32768 (default value)System priority

Load non-sharing (default

value)Load sharing

Non-revertive (default value)Revertive mode

Static LAG (default value)LAG type

NE1Parameter


50/56


Information About VLAN-Based E-Line Services

In this example, all the Ethernet services transmitted on the network carry VLAN tags. Therefore, Ethernet services

are configured as VLAN-based E-Line services on NE1, NE3, NE4, and NE5. For details on service planning, see

the following table.

120120120120110100, 110, and

120

Sink C-VLAN

ID

3-IFU2-14-IFU2-14-IFU2-13-IFU2-13-IFU2-11-EM6F-1Sink port

120110120120110100, 110, and

120

Source C-

VLAN ID

7-EM4T-17-EM4T-13-IFU2-17-EM4T-27-EM4T-13-IFU2-1Source port

Not transparently

transmitted

Not transparently

transmitted

Not transparently

transmitted

Not transparently

transmitted

Not transparently

transmitted

Not transparently

transmitted

BPDU

UNI-UNIUNI-UNIUNI-UNIUNI-UNIUNI-UNIUNI-UNIService

direction

E-Line-6E-Line-5E-Line-4E-Line-3E-Line-2E-Line-1Service name

654321Service ID

NodeB 5 to NE4NodeB 4 to NE2NE5 to NE2NodeB 3 to NE2NodeB 2 to NE2NE2 to the

RNC

NE5NE4NE3NE1Parameter

Information About IEEE 802 1q Bridge


51/56


Information About IEEE 802.1q Bridge-

Based E-LAN Services On the service aggregation node (NE3), where certain VLAN IDs conflict with each other, you need to configure the

Ethernet services as IEEE 802.1q bridge-based E-LAN services. For details on service planning, see the following table.

1-EM6T-3 (VLAN ID: 100)

3-IFU2-1 (VLAN ID: 110, 120)

4-IFU2-1 (VLAN ID: 110, 120)

Split horizon group

1-EM6T-3 (VLAN ID: 100)

3-IFU2-1 (VLAN ID: 110, 120)

4-IFU2-1 (VLAN ID: 110,120)

5-IFU2-1 (VLAN ID: 100, 110, 120)

UNI port connected to the

bridge

IVLMAC address learning

mode

EnabledMAC address self-learning

C-AwaredTAG attribute

E-LAN-1Service name

1Service ID

NE2Item

Q S (Diff )


52/56


QoS (Diffserv) Diffserv is the basis for configuring QoS. It is recommended that you allocated the VLAN priority or DSCP based on the type of

services on each NodeB. Then, create the corresponding DS domain on the transmission network based on the allocated VLAN

priority or DSCP. In addition, ensure that all the Ethernet ports that transmit the Ethernet services adopt the same DS

configurations.

In this example, the VLAN priority is configured for the services on each NodeB based on the service type. Then, each NE

allocates the corresponding PHB class to each service based on its VLAN priority. For details, see the following table. In addition,

all the Ethernet ports that transmit the Ethernet services adopt the same DS configurations.

HSDPA data services (HSPA interactive and HSPA background services)0BE

-1AF1

R99 non-real-time services (R99 interactive and R99 background services)2AF2

OM and HSDPA real-time services (OM streaming and HSPA streaming services)3AF3

-4AF4

Real-time voice service and signaling service (R99 conversational and R99 streaming

services)5EF

-6CS6

-7CS7

Corresponding Service TypeVLAN PriorityPHB Service Class

When mapping PHB service classes, do not use the CS7 queue if possible, because the CS7 queue may be used to transmit Ethernet

protocol packets or inband DCN packets.


53/56


QoS (Queue Scheduling Mode) Generally, all the Ethernet ports that transmit the Ethernet services adopt the same queue scheduling mode.

For the queue scheduling mode adopted by all the Ethernet ports in this example, see the following table.

SPBE

WRR (weight = 5)AF1

WRR (weight = 30)AF2

WRR (weight = 60)AF3

WRR (weight = 5)AF4

SPEF

SPCS6

SPCS7

Queue Scheduling ModePHB Service Class


54/56


QoS (CAR or Shaping for a Specific Service)

To perform CAR processing or shaping for a specific service, you generally need to perform corresponding

configurations only on the edge nodes of the DS domain.

In this example, CAR processing needs to be performed on the edge nodes of the DS domain for the R99 non-real-

time service (that is, the service with the VLAN priority of 2) on each NodeB in the uplink direction (that is, from the

NodeB to the RNC). For CAR parameters, see the following table.

In this example, traffic shaping also needs to be performed on the edge nodes of the DS domain for the OM and

HSDPA real-time services (that is, the services with the VLAN priority of 3) on each NodeB in the uplink direction (that

is, from the NodeB to the RNC). For parameters associated with traffic shaping, see the following table.

Mapping to the

EF queue

Mode of processing yellow

packets

10240 bytesPBS

8192 kbit/sPIR

5120 bytesCBS

4096 kbit/sCIR

ValueParameter

Table 1 CAR parameters Table 2 Parameters associated with traffic shaping

5120 bytesPBS

4096 kbit/sPIR

2560 bytesCBS

2048 kbit/sCIR

ValueParameter


55/56


Summary

This course focuses on the following points:

How to select Ethernet boards for OptiX RTN 900 V100R002 NEs

How to plan Ethernet services on a radio transmission network

comprised of OptiX RTN 900 V100R002 NEs How to plan port attributes of Ethernet boards on OptiX RTN 900

V100R002 NEs

Examples of planning and configuring Ethernet services on

Ethernet boards of OptiX RTN 900 V100R002 NEs


56/56

Thank youwww.huawei.com

Documents

OptiX RTN 900 V001R002 Ethernet Service Planning and Design Guide-20100114-A