03 Optix RTN 900 Qos Oam Introduction Issue 1.10

OptiX RTN 900 QoS &
OAM Introduction
www.huawei.com
Copyright © 2012 Huawei Technologies Co., Ltd. All rights reserved.

Objectives
 Upon completion of this course, you will be able to:
 Outline the QoS model
 Describe QoS basic concepts
 Outline the key technology in QoS
 Describe the typical QoS application in OptiX RTN900 network
 Explain the function of Ethernet/MPLS/ATM OAM
 Explain the function of MPLS-TP OAM
Copyright © 2012 Huawei Technologies Co., Ltd. All rights reserved. Page1
Contents
1. QoS Overview
2. QoS Models
3. QoS Technology
4. Application of QoS in OptiX 900 Equipment
5. OAM Feature Introduction
6. MPLS-TP OAM Introduction
Concept of QoS
 QoS: Quality of Service
 Transmission bandwidth
 Delay and jitter in transmission
 Packet loss
 Competition for resources in the network brings about the

requirement for QoS
 Enhancing quality of a service may degrade quality of other

services
Transmission Bandwidth
 BWmax = Min(100M,10M, 1M, 2M,1G) = 1Mbps
100Mbps 10Mbps 1Mbps 2Mbps 1Gbps
PC Server
BWmax = 1Mbps
 Barrel theory: the maximum bandwidth (BWmax ) equals the

minimum bandwidth on the data transmission link
End-to-End Delay
 The end-to-end delay is the sum of the transmission delay,
processing delay, and queue delay on the path
80 Km
Transmission delay
Processing & Queue delay
Jitter
 Jitter is caused by the difference between end-to-end delays of

packets in the same flow
Packet Loss
Packet Loss Packet Loss
 Packet loss may occur in the whole process of data transmission
Contents
1. QoS Overview
2. QoS Models
3. QoS Technology
QoS Models
 Best Effort
 Forwarding all the traffic with best-effort, without discrimination
 Integrated Service Model (IntServ Model)

 Reserve resources for each flow
 Maintain the forwarding status for each flow
 Differentiated Service Model (DiffServ Model)

 Classify and mark the flow
 Provide different services for different flows
Best-Effort Model
 Best-Effort is a single service model
 Using Best-Effort model can transfer any number of packets at

any time without getting previous approval
 There is no guarantee with respect to time delay and reliability
 It is implemented by first in and first out (FIFO) queue

technology
IntServ Model
 Provide controllable end-to-end service
 Network units support QoS control mechanism
 The application applies to NM for specific QoS service
 Signaling protocol deploys in network according to QoS

request
 RSVP is the most frequently used
DiffServ Model
Perform PHB according to
marking……
DS Domain
Perform PHB Set TCA according to SLA

Set TCA according to SLA according to Classify and mark traffic
Classify and mark traffic marking Monitor traffic
Monitor traffic
SLA & TCA
 SLA: Service Level Agreement
 Agreement signed by the ISP and the customer to stipulate the
treatment that the service flow of the customer should obtain on
the ISP's network
 TCA: Traffic Conditioning Agreement

 Agreement signed by the ISP and the customer to stipulate the
service classification rules, service model, and service processing
policy
Basic Concept of DiffServ
Term Description
Provide the same service policy and realize the same per-
DS Domain
hop behavior in the same domain
Edge Node The edge node of DS domain
Internal Node The internal node of DS domain
Per-hop behavior, the forwarding behavior description for

PHB
each node
PHB Level and QoS
PHB Level PHB QoS
BE Default PHB, FIFO (first in first out) and tail-drop
AF1 Assured Forwarding: Guarantees certain bandwidth
Permits occupation of idle bandwidth. Totally four classes, with three

AF2 levels of drop probability
E.g. AF11: Low drop precedence

AF3
AF12: Medium drop precedence
AF4 AF13: High drop precedence
EF Minimizes the delay;
CS6 Guarantees certain bandwidth for preferential services;
CS7 Discards extra traffic if the total traffic exceeds the specified bandwidth.
Questions
 What functions does QoS can provide?
 What kinds of models can be provided for implementing QoS ?
Contents
1. QoS Overview
2. QoS Models
3. QoS Technology
Contents
3. QoS Technology
3.1 Flow Classification
3.2 Traffic Policing & Traffic Shaping
3.3 Queue Scheduling
3.4 Congestion Avoidance
Flow Classification
 Through flow classification, the packets that meet different
types of characteristics can be identified according to certain
rules
 Flow classification method:
 Simple Flow Classification
 VLAN PRI, IP DSCP, MPLS EXP to PHB
 Complex Flow Classification

 ACL, based on MAC address, Source/Destination IP address, TCP/UDP
port number, protocol type
 C-VLAN/S-VLAN ID, C-VLAN/S-VLAN priority, or DSCP value
VLAN PRI Classification
DA SA TYPE DATA CRC Ethernet II Frame
DA SA TAG TYPE DATA CRC IEEE802.1Q
PRI
0x8100 CFI VLAN ID
3 bits
 IEEE 802.1P VLAN PRI: 3 bits, 0-7
MPLS Packet Classification
L2 Header MPLS Label L3 Header L3 Payload
Label Exp S TTL
0 19 22 23 31
 MPLS Exp: 3 bits, 0-7
IP Packet Classification
32bits
8 8 8 8
Version Header Type of Service Total Length
(4bits) Length (8bits) (16bits)
Identifier Flags Fragmented Offset
(16bits) (3bits)
Time to Live Protocol Header Checksum
(8bits) (8bits) (16bits)
Source IP Address
(32bits)
Destination IP Address
(32bits)
Options
(Variable Length)
DSCP: DiffServ Code Point
 DSCP: DiffServ Code Point
 Each DSCP value maps one BA
 Each BA has its own PHB
 Each PHB correspond to its own QoS policy
DSCP (RFC2474)
R R
Marking
 After traffic classification, different traffic can be re-marked by
different ways:
 IP packets: Re-marking is used to set the DSCP of an IP packet
 MPLS packets: Re-marking is used to set the EXP field of an MPLS

packet.
 For VLAN packets: Re-marking is used to set the 802.1P flag bit of
a VLAN packet
Traffic Policing & Traffic Shaping
 Traffic Policing
 Monitor the traffic at the network edge and limit the traffic in a
range. If the traffic of a connection exceeds the limit, the device
drops the packets or re-mark the precedence of the packets
 Traffic Shaping
 The function of traffic shaping is similar to the function of traffic
policing. Traffic shaping will store the packets exceeds the limit
into cache
Application of Traffic Policing and
Traffic Shaping
Traffic policing
Network 1
Egress
Network 2
Ingress
NEA NEB
Traffic shaping
Token Bucket
 The token bucket is used to assess whether the traffic exceeds
the specified limit corresponding measures
 Token bucket uses the following parameters to assess the
traffic:
 CIR (Committed Information Rate): the rate at which tokens are
added to the bucket
 CBS (Committed Burst Size): capacity of the token bucket, namely
the maximum size allowed for a traffic burst. The CBS must be
larger than the packet length
CAR: Committed Access Rate
Forward
Classification
Pass
Packets without traffic policing
Packets with traffic policing Drop
Token Bucket - Dual Buckets
Tokens Tokens
(PIR) (CIR)
Tp Tc
(PBS) (CBS)
Packets
Classification
PIR
CIR
GTS: Generic Traffic Shaping
Packets to be sent
from the interface
Packets Out
Classification
Pass
Token
Bucket
Packets without traffic shaping
Packets with traffic shaping GTS Queue
Drop
Queue Scheduling
 Put packets into different queues according to their priority,
and give different dispatch priorities, or bandwidths etc. to
different queues
 FIFO (First In First Out)
 SP (Strict-Priority )
 WRR (Weighted Round Robin )
FIFO: First In First Out
 FIFO queuing
 Concepts of no communication priority and classification
 FIFO is the default queuing
Packet need to be forwarded
Urgent packets
Hypo-urgent packets
Non-urgent packets
SP: Strict-Priority
 SP guarantees that the data packet with higher priority can be
sent in time
 SP is divided into different queues (For example : 4 queues): High,
Medium, Normal, Low
 High priority queues will be first dispatched
Classification
High
Medium
Normal
Low Drop
WRR: Weighted Round Robin
 WRR assures justice to services with identical priority
 The weight is based on the priority
Classification
High
Medium
Normal
Low Drop
Congestion Avoidance Mechanism
 Tail drop
 When the queue length reaches the maximum value, the new
arrived packets are dropped
 RED: Random Early Detection
 WRED: Weighted Random Early Detection
Disadvantages of Tail Drop
 TCP global synchronization
 TCP starvation
 High delay and high jitter
 Non-differentiated drop
Bandwidth
Utilization Ratio
User flow
time t
RED: Random Early Detection
Drop Not drop Random drop Tail drop

probability
100%
10% Max. drop probability
20 40 Average queue length

(low limit) (high limit)
WRED: Weighted Random Early
Detection
Drop
probability
100%
10% Max. drop probability
20 25 30 35 40 Average queue length
AF21
AF22
AF23
Questions
 What can be used to classify different traffic?
 Please describe the different queues and their characters?
Contents
1. QoS Overview
2. QoS Models
3. QoS Technology
Flow Classification
 Simple flow classification
 VLAN priority, IP DSCP, MPLS Exp
 Complex flow classification

 C-VLAN/S-VLAN ID, C-VLAN/S-VLAN priority, or DSCP value
RTN 900 Traffic Policing
 CAR
 Committed Access Rate
 CIR
 Committed Information Rate
 PIR
 Peak Information Rate
RTN 900 Queue Scheduling
 SP: strict-priority
 For queues of highest priorities, which carry CS7, CS6 or EF packets, use
the SP scheme to schedule queues
 WRR: weighted round robin

 For queues of higher priorities, which carry AF4, AF3, AF2 and AF1
packets, use the WRR scheme to schedule queues
 Note:
 For BE packets, the QoS is not ensured. In the case of congestion, the RTN
900 equipment does not schedule queues that provide this service level
(BE)
RTN 900 Congestion Avoidance
 Packet discarding policies are available in RTN 900
 Trail drop policy: RTN 900 V1R2/V1R3/V1R5 support.
 Weighted random early detection (WRED) policy: RTN 900 V1R1

support.
RTN 900 QoS Policy
 For the RTN 900 equipment, the configurable QoS policies
include:
 Port policy
 V-UNI ingress policy / V-UNI egress policy
 PW policy / QinQ policy
 ATM policy
 WRR scheduling policy
Questions
 Which QoS policy can be used to realize the end to end QoS
control for the RTN 900 equipment?
Contents
1. QoS Overview
2. QoS Models
3. QoS Technology
Contents
5. OAM Technology
5.1 Ethernet OAM
5.2 MPLS OAM
5.3 ATM OAM
Typical Application of ETH OAM
Ethernet Port OAM Ethernet Port OAM
Ethernet Service OAM
P P
Router 1
CE1 CE3 Router 3
PE2
PE1
P P
CE2 CE4
Router 2
 As a protocol based on the MAC layer, ETH OAM checks Ethernet links by
transmitting OAM protocol packets.
Ethernet Port OAM
 The Ethernet port OAM is mainly used to check the connectivity and
performance and locate the faults of the physical links at the MAC layer and
under the MAC layer. It is applicable to the physical Ethernet connection, not
to the connections between port and VCG, nor between VCG and VCG.
PORT VCG VCG PORT
Board Board
OAM PDU interworking available OAM PDU interworking unavailable
Basic Concept
 OAMPDU (OAM Protocol Data Unit)
 All functions of IEEE 802.3ah OAM are realized by exchanging the
OAMPDUs
 OAM mode:
 Active/ Passive mode
Ethernet Port OAM Auto-Discovery
Active Passive
Node 1 Node 2
1. Node 1 initiates the

discovering actively and
transmits the packets 2. After receiving the packets from
that carry information Node 1, Node 2 compares the
about Node 1. packets with the local end and
judges whether the setting
meets the requirements. Then,
it transmits the OAM packets
that carry the information
3. After receiving response about Node 1and Node 2.
packet from Node 2, Node
1 renews the information of
Node 2 locally. OAMPDU sent by Node 1
OAMPDU sent by Node 2
Ethernet Port OAM – Link Monitoring
Node 1 Node 2
1. Node 1 sends packet

carrying information of
signal degraded event .
2. If there is signal degraded event

detected, ETHOAM_RMT_SD
will be reported.
Ethernet Port OAM – Remote Fault
Report
Node 1 Node 2
1. Node 1 detects failure

at local end, then sends
OAM packet to opposite
node.
2. Node 2 detects the fault and

reports the event.
Ethernet Port OAM – Remote Loopback
Active Passive
Node 1 Node 2
1. Node 1 originates
remote loopback
request actively.
2. After receiving the loopback

request packet from Node 1,
Node 2 enters the loopback
state and sends the loopback
response packet to Node 1.
3. After receiving the

loopback response packet
from Node 2, Node 1
enters the loopback state. OAMPDU sent by Node 1
Ethernet Port OAM – Self-loop Test
Tx
When the self-loop detection is
PORT
enabled for an external physical port,
Rx if the self-loop situation occurs at the
port, the ETHOAM_SELF_LOOP alarm
PORT is reported.
Rx
When the self-loop detection is

enabled for a system-side VCTRUNK
port, if the self-loop situation occurs
VCG at the port, the
ETHOAM_VCG_SELF_LOOP alarm is
reported.
Ethernet Service OAM
 The Ethernet service OAM, based on the Ethernet service traffic,
is used to provide the automatic check, fault location and
performance check for the connectivity of the Ethernet link.
 The main functions of Ethernet Service OAM:

 Fault detection (Continuity Check, short for CC)
 Fault identification (LoopBack, short for LB)
 Fault location and isolation (LinkTrace, short for LT)
Basic Concepts of Ethernet Service OAM
CE CE
PE PE
5 5 5 5
Customer MD Level
3 3
The number indicates
Service Provider MD Level
the MD level
MA MEP MIP
Ethernet Service OAM - CC
 CC: Perform unidirectional connectivity check (CC)
 After receiving the CCM packets, the sink MEP starts the CC.
 If the sink MEP fails to receive the CCM packets from the source MEP
within the check period (that is, 3.5 times of the transmit period), it
reports the CC_LOS alarm automatically till the link restores normality
EX_ETHOAM_CC_LOS
MEP1 MIP1 MIP2 MIP3 MIP4 MEP2
Ethernet Service OAM - LB
 LB: Perform the loopback (LB) detection
 After receiving the LBM packets, the sink MP constructs the loopback
return (LBR) packets and transmits them back to the source MEP. In this
case, the loopback succeeds. If the source MEP timer expires and fails to
receive the LBR from the sink MP, the loopback fails.
Failed
LBM LBR
Ethernet Service OAM - LT
 LT: Perform the link trace (LT) detection.
Failed
LTM
LTM
LTR2 LTM
LTR3 LTM
LTR4 LTM
LTR5
LTR6
Contents
5. OAM Technology
5.1 Ethernet OAM
5.2 MPLS OAM
5.3 ATM OAM
Overview of MPLS Layer
 As shown in the below figure, in the OptiX RTN 900 network ,
services could be transferred in a PW, and many PWs could be carried
by a MPLS tunnel.
 For the expected network maintenance, OAM function should be
provided in both the MPLS tunnel layer and the PW layer.
Service 1
PW MPLS Tunnel
Service 2
Packet Types
 CV Packet
 Checks the connectivity of LSPs
 The transmit frequency is fixed
 FFD Packet
 Checks the connectivity of LSPs
 The transmit frequency can be changed
 FDI Packet
 Responds to the defect that the CV or FFD packet detects
 BDI Packet
 Carries defect information to the upstream ingress node
MPLS OAM – Connectivity Check
 The connectivity of a label switch path (LSP) can be checked by a
connectivity verification (CV) or fast failure detection (FFD).
 The CV and FFD processes are the same except for that CV packets are
transmitted always at a rate (1 frame/s, not for setting) whereas FFD
packets are transmitted at a user-defined rate.
Transit Transit
LSR CV/FFD LSR
CV/FFD CV/FFD
Ingress Egress
LSR LSR
BDI BDI
BDI
Transit Transit
LSR LSR
Tunnel OAM – Connectivity Check
 MPLS tunnel OAM is a unidirectional connectivity detection
mechanism for a single LSP. The BDI packet should be carried by
another reverse LSP.
 OAM packets are encapsulated in MPLS packets at the Ingress LSR. The
external label is the outgoing label of the LSP at the Ingress LSR.
CV/FFD CV/FFD
Insertion Extraction
Ingress Transit Egress
Label Push LSR LSR LSR Label Pop
Monitored LSP Monitored LSP

Customer Customer
Traffic Traffic
BDI BDI
Transit
LSR
PW OAM – Connectivity Check
 PW OAM CV/FFD is a unidirectional real-time connectivity detection
mechanism for a PW. It is necessary that the source and the
destination both enable PW CV/FFD.
 OAM packets are encapsulated in MPLS packets at the Ingress LSR.
CV/FFD CV/FFD
Insertion Extraction
Label Push Ingress Transit Egress
LSR LSR LSR Label Pop
Monitored LSP Monitored LSP

Customer Customer
Traffic BDI BDI Traffic
MPLS OAM – BDI/FDI
 BDI: Inform the ingress node of the LSP defect information
Node B
RTN 900 Network RTN 900 Network
RNC
Node B CV/FFD
BDI
 FDI: Inform the egress node of the LSP of the default information of a lower
layer
Node B
RNC
Node B CV/FFD
FDI
MPLS OAM – Ping
 The MPLS ping function is used to check whether an LSP is
successfully created
Node B
RNC
Node B MPLS Echo Request
MPLS Echo Reply
Ingress LSR Transit LSR Egress LSR
MPLS Echo Request

MPLS Echo Reply
MPLS OAM – Traceroute
 The MPLS traceroute function is used to locate an LSP fault
Node B
RNC
Node B MPLS Echo Request
MPLS Echo Reply
Ingress LSR Transit LSR Egress LSR
MPLS Echo Request

(TTL=1)
MPLS Echo Reply
MPLS Echo Request
(TTL=2)
MPLS Echo Reply
Contents
5. OAM Technology
5.1 Ethernet OAM
5.2 MPLS OAM
5.3 ATM OAM
Overview of ATM OAM
Node B
RNC
Node B
Node B RNC
Node B
ATM Service OAM
ATM OAM Function Layers
Layer Description
F1: regenerator section layer Physical layer OAM: The physical layer OAM flow
F2: digital section layer depends on the transmission mechanism of a specific

transmission system.
F3: transmission channel layer
An ATM network contains the following three types
of transmission mechanisms:
1. SDH-based transmission system
2. Cell-based transmission system
3. PDH-based transmission system
F4: virtual path (VP) layer ATM OAM: The ATM OAM is based on the VP/VC
F5: virtual channel (VC) layer and independent of the transmission system.
Basic Concepts of ATM OAM
Node B RNC
Endpoint Segment Non Segment Non Segment Segment

Point and Endpoint and Endpoint and Endpoint
Point Point
Segment
End to End
ATM OAM – AIS/RDI Insertion
Node 1 Node 2 Node 3
AIS Inserted AIS Reported
1 2 3
A B C D
RDI Reported
RDI Inserted
Segment Point or Endpoint Non Segment and Endpoint
ATM OAM - CC
 CC: Perform unidirectional connectivity check (CC)
Failed
AIS Inserted
1 2 3
A B C D
Segment Point or Endpoint Non Segment and Endpoint
ATM OAM - LB
 LB: Perform the loopback (LB) detection.
1 2 3
A B C D E
Succeeded
Failed
A B C D E
Summary
OAM Type Usage Application Scenario
Bidirectional connectivity check and
Ethernet performance of the physical link Link state monitoring
Port OAM
Port OAM monitoring
Real-time detection of the link state
CC Unidirectional connectivity check
monitoring
Ethernet
Service Fault location or detection at a single
LB Bidirectional connectivity check
OAM end
LT Fault location On-site fault location
Real-time detection of the tunnel state
CV/FFD Unidirectional connectivity check
monitoring
MPLS Fault location or detection at a single
OAM Ping Unidirectional connectivity check
end
Traceroute Fault location Tunnel route detection
Real-time detection of the link state
CC Unidirectional connectivity check
ATM monitoring
OAM Fault location or detection at a single
LB Bidirectional connectivity check
end
Contents
1. QoS Overview
2. QoS Models
3. QoS Technology
MPLS-TP OAM Introduction
 MPLS-TP OAM is the new OAM feature for RTN 900V1R5
 MPLS-TP (OAM) can effectively detect, identify, and locate

faults on packet switched networks and notify related NEs of
the faults
 MPLS-TP OAM functions include the following proactive OAM

functions and on-demand OAM functions:
 continuity check (CC), remote defect indication (RDI), alarm
indication signal (AIS), loopback (LB), link trace (LT), loss
measurement (LM), and delay measurement (DM).
MPLS-TP OAM Protocol Model
MPLS-TP OAM Components
 MEG (Maintenance Entity Group)
 MEG is a set of entity run the OAM, it can carry the MEG ID
information in it’s PDU
 MEP (MEG End Point)

 MEPs mark the source and sink nodes of a MEG and are capable
of initiating and terminating OAM frames
 MIP (MEG Intermediate Point)

 A MIP is an intermediate point in a MEG and is capable of
responding to or forwarding some OAM frames
MPLS-TP OAM PDU Formats
 Format of an MPLS-TP tunnel OAM PDU
MPLS-TP OAM PDU Formats(Cont.)
 Format of an MPLS-TP PW OAM PDU
MPLS-TP OAM - CC
 CC is used to detect unidirectional connectivity between any
pair of MEPs in MEGs.
 A pair of MEPs periodically transmit and receive CCM frames to

achieve CC
MEP1 MEP2 LOCV
×
CCM
MPLS-TP
MPLS-TP OAM - RDI
 A maintenance association end point (MEP), upon detecting a
defect condition, notifies its peer MEP of the defect condition.
Upon receiving the notification, the peer MEP reports a remote
defect indicator (RDI) alarm
RDI MEP1 MEP2 LOCV
×
CCM
MPLS-TP
RDI
MPLS-TP OAM - AIS
 A server layer MEP, upon detecting a defect condition,
transmits AIS frames to its client layer MEs, so its client layer
MEPs suppress alarms following detection of the defect
condition at the server layer. Upon receiving an AIS frame, a
client layer MEP reports an AIS alarm
The AIS insertion Reports the
Sends OAM function is MPLS_TUNNEL_LOCV
detection enabled alarm
packets MEP1 MIP2 MEP3
× TUNNEL1 TUNNEL2
The MIP detects a fault Reports the

MPLS_TUNNEL_AIS
OAM detection packet
and insert an AIS
packet to downstream alarm
AIS packet
MPLS-TP OAM – AIS (Cont.)
 PW AIS triggered by the tunnel failure
MS-PW is
configured and
the AIS insertion Reports the
Sends OAM function is MPLS_PW_LOCV
detection enabled alarm
packets MEP1 MIP2 MEP3
The MIP detects a Reports the OAM detection packet

fault and insert an AIS MPLS_PW_AIS
packet to downstream alarm
AIS packet
MPLS-TP OAM – LB
 A loopback (LB) test is used to check bidirectional connectivity
of links between a maintenance association end point (MEP)
and a maintenance association intermediate point (MIP) or
between a pair of MEPs.
MEP1 LBM MIP2 LBM MIP3 MEP4

(TTL=2) (TTL=1)
LBR LBR
(TTL=254) (TTL=255)
MPLS-TP OAM – LT
 An LT test is achieved by a series of LB tests that are
implemented from near to far. It is used to obtain the
adjacency relationship between a MEP and a MIP or between a
pair of MEPs and to locate the link or device fault between the
two.
MEP1 LBM MIP2 LBM MIP3 LBM MEP4

(TTL=3,SN=3))
(TTL=1,SN=1
(TTL=2,SN=2) (TTL=2,SN=3)
(TTL=1,SN=2) (TTL=1,SN=3)
LBR LBR LBR

(TTL=254,SN=2
(TTL=255,SN=1 )
(TTL=253,SN=3 (TTL=254,SN=3
(TTL=255,SN=2 ) (TTL=255,SN=3 )
MPLS-TP OAM – LM
 LM is used to count lost packets on a tunnel or PW within a
specified period of time.
MPLS-TP OAM – DM
 Two-way DM is used to measure frame delay and frame delay
variation of bidirectional data frames on a link within a
specified period of time.
Summary
 QoS Models
 QoS technology
 Application of QoS in RTN 900 Equipment
 Ethernet OAM
 MPLS OAM
 ATM OAM
 MPLS-TP OAM
Glossary
 QoS: Quality of Service
 IntServ: Integrated Service Model
 DiffServ: Differentiated Service Model
 RSVP: Resource Reservation Protocol
 PHB: Per-Hop Behavior
 EF: Expedite Forwarding
 CS: Class selector
 AF: Assure Forwarding
Glossary (Cont.)
 OAM: Operation, administration and maintenance
 CC: Continuity Check
 LB: Loop Back
 LT: Link Trace
 CV: Connectivity Verification
 FFD: Fast Failure Detection
 LSP: Label Switch Path
Thank you
www.huawei.com

03 Optix RTN 900 Qos Oam Introduction Issue 1.10

Uploaded by

Document Information

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

03 Optix RTN 900 Qos Oam Introduction Issue 1.10

Uploaded by

Copyright:

Available Formats

OptiX RTN 900 QoS &

Copyright © 2012 Huawei Technologies Co., Ltd. All rights reserved.

 Describe QoS basic concepts

 Outline the key technology in QoS

 Describe the typical QoS application in OptiX RTN900 network

 Explain the function of Ethernet/MPLS/ATM OAM

 Explain the function of MPLS-TP OAM

4. Application of QoS in OptiX 900 Equipment

5. OAM Feature Introduction

6. MPLS-TP OAM Introduction

 Delay and jitter in transmission

 Competition for resources in the network brings about the

 Enhancing quality of a service may degrade quality of other

100Mbps 10Mbps 1Mbps 2Mbps 1Gbps

 Barrel theory: the maximum bandwidth (BWmax ) equals the

Processing & Queue delay

 Jitter is caused by the difference between end-to-end delays of

Packet Loss Packet Loss

 Packet loss may occur in the whole process of data transmission

4. Application of QoS in OptiX 900 Equipment

5. OAM Feature Introduction

6. MPLS-TP OAM Introduction

 Integrated Service Model (IntServ Model)

 Differentiated Service Model (DiffServ Model)

 Using Best-Effort model can transfer any number of packets at

 There is no guarantee with respect to time delay and reliability

 It is implemented by first in and first out (FIFO) queue

 Network units support QoS control mechanism

 The application applies to NM for specific QoS service

 Signaling protocol deploys in network according to QoS

 RSVP is the most frequently used

Perform PHB Set TCA according to SLA

 TCA: Traffic Conditioning Agreement

Edge Node The edge node of DS domain

Internal Node The internal node of DS domain

Per-hop behavior, the forwarding behavior description for

BE Default PHB, FIFO (first in first out) and tail-drop

AF1 Assured Forwarding: Guarantees certain bandwidth

Permits occupation of idle bandwidth. Totally four classes, with three

E.g. AF11: Low drop precedence

EF Minimizes the delay;

CS6 Guarantees certain bandwidth for preferential services;

 What kinds of models can be provided for implementing QoS ?

4. Application of QoS in OptiX 900 Equipment

5. OAM Feature Introduction

6. MPLS-TP OAM Introduction

3.2 Traffic Policing & Traffic Shaping

3.3 Queue Scheduling

3.4 Congestion Avoidance

 Complex Flow Classification

DA SA TYPE DATA CRC Ethernet II Frame

DA SA TAG TYPE DATA CRC IEEE802.1Q

 IEEE 802.1P VLAN PRI: 3 bits, 0-7

L2 Header MPLS Label L3 Header L3 Payload

Label Exp S TTL

 MPLS Exp: 3 bits, 0-7

 Each BA has its own PHB

 Each PHB correspond to its own QoS policy

 MPLS packets: Re-marking is used to set the EXP field of an MPLS

Packets without traffic policing

Packets with traffic policing Drop

Packets without traffic shaping

Packets with traffic shaping GTS Queue