Configuring Quality of Service (QoS)

MINI-LINK 6352

Operating Instructions

11/1543-HRA 901 17/7 Uen V

Copyright

© Ericsson AB 2013–2018. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of this
document.

11/1543-HRA 901 17/7 Uen V | 2019-06-27

 Contents

Contents

1 Quality of Service Overview 1

1.1 Classification 3
1.2 Marking 3
1.3 Policing 4
1.4 Mapping Operator Priority to Priority Queue 5
1.5 Queuing 5
1.6 Scheduling 6
1.7 Shaping 8

2 Planning and Preparing 9

2.1 Prerequisites 9
2.2 Limitations 9
2.3 Planning Advice 9
2.4 Required Documentation 9

3 CLI Configuration 10
3.1 Classifying and Marking the Traffic 10
3.2 Configuring Queuing with WRED (CLI) 15
3.3 Configuring Scheduling 16
3.4 Configuring Shaping (CLI) 19
3.5 Setting the Frame Size (CLI) 19

4 Node GUI Configuration 21

4.1 Configuring Scheduling 21

11/1543-HRA 901 17/7 Uen V | 2019-06-27

Configuring Quality of Service (QoS)

11/1543-HRA 901 17/7 Uen V | 2019-06-27

 Quality of Service Overview

1 Quality of Service Overview

Quality of Service (QoS) is a set of mechanisms that makes it possible to prioritize

Ethernet frames depending on traffic type, and to make sure that the capacity is
sufficient to guarantee a congestion-free network. QoS is an alternative to
overprovisioning the network.

A network is logically separated in an operator domain and one or more customer

domains, as in the example in Figure 1.

Customer Customer
Domain
Operator Domain Domain

Customer Operator Customer

Priority Priority Priority

Figure 1 Customer and Operator Domains

The priority of a frame in an end-to-end Ethernet connection can be different in

different parts of the network. Customers set the priority to use in their domains,
and the operator sets the priority to use in the operator domain.

Figure 2 shows an overview of the QoS mechanisms that the packet radio
supports.

11/1543-HRA 901 17/7 Uen V | 2019-06-27 1

 Configuring Quality of Service (QoS)

Classification Marking

Trusted
customer Mapping
Frame
priority tables
ingress
MPLS
Operator
priority
DSCP
INGRESS
PCP

Default
Classification priority
disabled or
no trusted
customer priority

Switching

Queueing Mapping operator priority Queueing Scheduling Shaping

• Tail dropping to priority queue • Aging
• WRED

Ethernet
egress
port

Priority queue 7

Mapping Priority queue 6

EGRESS table

Priority queue 5 Frame

egress
Shaping
Priority queue 4 buffer
Frame Frame
dropping Priority queue 3 dropping

Priority queue 2

Priority queue 1

Priority queue 0

Figure 2 Overview of the QoS Mechanisms

The size of an Ethernet frame is often related to the end-user application. A real-
time application (for example, voice, video) that requires minimum latency
typically uses small Ethernet frames, while a data application with no real-time
characteristics uses the maximum frame size. The system supports multicast,
unicast, and broadcast frames, and supports frames with a size up to 9,216 bytes
(Jumbo Frames).

2 11/1543-HRA 901 17/7 Uen V | 2019-06-27

 Quality of Service Overview

The system supports priority handling according to IEEE802.1Q 2005 and

IEEE802.1D 2004. Priority is a representation of the end-user application, for
example, voice or best-effort data, and is used to differentiate the handling of
different traffic types. Each traffic type is associated with a priority value to
indicate the relative importance of that traffic type. The traffic types and
associated priority values are standardized in IEEE802.1Q 2005 and IEEE802.1D
2004. In a network, it is important to only use one set of priority definitions (for
example, IEEE 802.1D 2004). Otherwise, the handling of traffic types can differ
between parts of the network in a non-predictable way.

1.1 Classification
The classification mechanism extracts customer priority in frames that enter the
operator domain.

The classification mechanism can extract the following types of customer

priority:

— MPLS TC value in the MPLS header

— IPv4 or IPv6 DSCP value in the IP header

— PCP value in the C-tag or S-tag of the Ethernet header

In a network with mixed traffic, the classification mechanism can extract the
different customer priority types simultaneously. The classification mechanism
then selects which customer priority to use in the following priority order:

— MPLS TC

— IPv4 or IPv6 DSCP

— PCP

1.2 Marking
The marking mechanism sets the operator priority.

If a frame contains trusted customer priority, the marking mechanism can use the
customer priority together with a mapping table to set the operator priority.

Note: It is only possible to configure a common priority mapping of DSCP

values for both IPv4 and IPv6.

The marking mechanism sets the operator priority to the default priority in the
following cases:

— the classification mechanism is disabled

11/1543-HRA 901 17/7 Uen V | 2019-06-27 3

 Configuring Quality of Service (QoS)

— no trusted customer priority included in the frame

1.3 Policing
The policing mechanism makes sure that a customer does not use more than the
allowed resources in a network.

The policing mechanism limits the input bit rates based on a bandwidth profile.
The bandwidth profiles support the MEF concepts Committed Information Rate
(CIR), Committed Burst Size (CBS), Excess Information Rate (EIR), and Excess
Burst Size (EBS). The policing mechanism drops excess traffic if the bit rate
reaches the configured maximum bit rate, see Figure 3.

Figure 3 Policing

The coloring process uses the above parameters in the following manner to
identify the appropriate color for a frame:

— Green frames: Input Rate<CIR and Burst Size<CBS

— CIR<Input Rate<EIR+CIR and CBS<Burst Size<EBS

— Input Rate>EIR or Burst Size>EBS

A graphical presentation of the coloring criteria is illustrated in .

4 11/1543-HRA 901 17/7 Uen V | 2019-06-27

 Quality of Service Overview

Traffic rate
[BPS]
>EBS
CIR +EIR CIR +EIR
CBS EBS
<CBS <EBS
CBS
CIR CIR

Time

Figure 4 Coloring of Frames in the Policing Function

The color information or drop eligibility in a network can be either explicitly or

implicitly encoded in the S-VLAN tag. Drop eligibility can be encoded with the
priority in the PCP field of the S-tag as specified for the C-tag, or it can be
encoded explicitly by using the Drop Eligible Indicator (DEI) bit in the S-tag.

The policing mechanism supports bandwidth profiles for MEF services in one of
the following ways:

— Per UNI

— Per UNI + CoS

— Per EVC

For configuration information, see Configuring Ethernet Services.

1.4 Mapping Operator Priority to Priority Queue

The Ethernet egress port has eight priority queues (also known as Traffic Classes
(TCs)). The mechanism for mapping operator priority to priority queue uses a
mapping table to forward frames to the correct priority queue. To handle
temporary link congestion, the Ethernet egress port has a buffer. The priority
queues share the buffer capacity.

1.5 Queuing
The queuing mechanism supports the following queue management mechanisms
for the priority queues:

— Tail dropping handles discarding of frames during long-term congestion that

fills the buffer completely. When a priority queue is full, the tail dropping
mechanism ensures that new frames are dropped at the entry point of the
priority queue.

— Weighted Random Early Detection (WRED) can increase the average

throughput in a TCP connection by minimizing the throughput variations and
avoiding tail drop. The WRED mechanism randomly discards frames when
the buffer is filled up to a configurable level. If the buffer filling continues to
increase the drop probability increases, see Figure 5. The buffer filling is
calculated as an average value, estimated over a certain period of time. This

11/1543-HRA 901 17/7 Uen V | 2019-06-27 5

 Configuring Quality of Service (QoS)

is a more accurate way of measuring buffer than for instance instant

measurements.

Probability of
dropping
incoming packet

100%

Maximum
Probability
Red

Maximum
Probability
Yellow

Maximum
Probability
Green

Minimum Minimum Maximum Minimum Maximum Maximum Average queue size (packets)
Threshold Threshold Threshold threshold Threshold Threshold
Red Yellow Red Green Yellow Green

Figure 5 Color Aware WRED Parameters

WRED can be enabled on ports with deep buffer.

If Color-aware WRED is used to regulate the queue, then different WRED

profiles can be applied for green and yellow traffic.

— Aging is useful for discarding old frames in delay-sensitive traffic, and

preventing propagation of useless frames in the network. The aging
mechanism uses timestamps and an aging timer to discard old frames.

It is possible to combine queue management mechanisms in order to get the

required behavior. However, from a simplicity point of view, it is recommended
that Aging is not configured together with WRED, since the dynamic buffer
handling schemas can end up in a behavior that was not anticipated.

1.6 Scheduling
The scheduling mechanism handles congestion by emptying the priority queues
according to one or both of the following algorithms:

— Strict Priority (SP) always schedules frames from the queue with the highest
priority first. SP is typically used for delay-sensitive traffic like voice, video,
and sync packets.

— Weighted Fair Queuing (WFQ) schedules frames in a flexible way, and

prevents starvation of priority queues. The WFQ algorithm is typically used
for data traffic that is not delay sensitive.

When using WFQ, the allocated bandwidth for a queue is its weight divided
by the sum of all weights for all queues. A scheduler handling N queues is

6 11/1543-HRA 901 17/7 Uen V | 2019-06-27

 Quality of Service Overview

configured with weight W for each queue i. The allocated bandwidth in

percent for queue i is calculated as: Wi ÷ (W1 + W2 + ... + WN) × 100.

With SP, low-priority queues will never get served if high-priority queues are
constantly being filled up. WFQ, however, makes sure that all queues are served
according to their predefined weight.

The scheduling mechanism can be set up to work with one set of high-priority SP
queues, one set of WFQ queues, and optionally one low-priority SP queue, as in
the example in Figure 6.

Ethernet egress buffer

Priority queue 7 Empty first

High-priority SP queues Priority queue 6 Empty second

Priority queue 5 Empty third

Priority queue 4 Serve 40%

Priority queue 3 Serve 30%

WFQ queues
Priority queue 2 Serve 20%

Priority queue 1 Serve 10%

Low-priority SP queue Priority queue 0 Empty last

Figure 6 Example of Combined SP and WFQ Scheduling

The number of queues of each type is configurable (see Table 1), but the
scheduling mechanism always empties the priority queues in the following order:

— high-priority SP queues

— WFQ queues according to weight

— low-priority SP queue (if one exists) according to best effort

11/1543-HRA 901 17/7 Uen V | 2019-06-27 7

 Configuring Quality of Service (QoS)

Table 1 Supported Combinations of SP and WFQ Priority Queues

Number of high-priority Number of WFQ queues Number of low-priority
SP queues SP queues
8 0 0
0 8 0
2 6 0
3 5 0
3 4 1
4 3 1

1.7 Shaping
The shaping mechanism enforces a bit rate that is lower than the line rate of the
physical interface. The mechanism buffers excess frames and schedules them for
later transmission. Shaping results in a smoother frame output bit rate, see Figure
7.

Figure 7 Shaping

The packet radio supports shaping on the LAN and WAN ports.

8 11/1543-HRA 901 17/7 Uen V | 2019-06-27

 Planning and Preparing

2 Planning and Preparing

This section includes information about required preparation before configuring

QoS

2.1 Prerequisites
This feature is included in Basic SW license. No additional license is required.

2.2 Limitations
This document only describes how to configure QoS for Ethernet and tasks
related to this. The radio link must be configured before the configuration of QoS
can start.

2.3 Planning Advice

To ensure proper node and network function, all configuration activities must be
planned in advance by skilled personnel.

— Read through all applicable chapters and make sure referenced documents
are available. For detailed commands, refer to CLI User Guide.

— Make sure you have access to the Network Element (NE) using CLI. For
detailed information, refer to Accessing a Network Element.

2.4 Required Documentation

Read through this document. Make sure that referenced documentation is
available during the configuration process by having the electronic CPI library
available on your PC. See Library Description for information on how to make the
CPI library available.

The following additional information is applicable when using CLI commands:

— How to start a CLI session and CLI basics, see CLI User Guide.

— For a detailed description of each CLI command, see CLI Descriptions.

11/1543-HRA 901 17/7 Uen V | 2019-06-27 9

 Configuring Quality of Service (QoS)

3 CLI Configuration

3.1 Classifying and Marking the Traffic

The following subsections show how to classify and mark the traffic using
different types of customer priority.

In a network with mixed traffic, the classification mechanism can extract the
different customer priority types simultaneously. The classification mechanism
then selects which customer priority to use in the following priority order:

— MPLS TC

— IPv4 or IPv6 DSCP

— PCP

3.1.1 Classifying and Marking Traffic using MPLS (CLI)

The valid values for MPLS are 0–7. Table 2 shows the default mapping table for
MPLS to operator priority.

Table 2 Default Mapping Table for MPLS to Operator Priority

MPLS Operator Priority
0 0
1 1
2 2
3 3
4 4
5 5
6 6
7 7

Example 1
# Set the customer priority classification:
#
# This example sets the customer priority classification to MPLS:
#
end; config slot 1 lan 1 2 priority mplsexp

# Change the mapping of MPLS to operator priority:

10 11/1543-HRA 901 17/7 Uen V | 2019-06-27

 CLI Configuration

#
# This example changes the mapping of MPLS TC 0, 1, and 5
# to operator priority 3, 4, and 7, respectively:
#
end; config slot 1 lan 1 2 mpls-exp-config mpls-exp-decode 0 priority 3
end; config slot 1 lan 1 2 mpls-exp-config mpls-exp-decode 1 priority 4
end; config slot 1 lan 1 2 mpls-exp-config mpls-exp-decode 5 priority 7

3.1.2 Classifying and Marking Traffic Using DSCP (CLI)

The valid values for DSCP are 0–63. Table 3 shows the default mapping table for
DSCP to operator priority.

Table 3 Default Mapping Table for DSCP to Operator Priority

DSCP Operator Priority
0-7 0
8-15 1
16-23 2
24-31 3
32-39 4
40-47 5
48-55 6
56-63 7

The classification mechanism can extract the following types of DSCP customer
priority:

— IPv4

— IPv6

— IPv4 and IPv6 combined

Example 2
# Set the customer priority classification:
#
# This example sets the customer priority classification to IPv6 DSCP:
#
end; config slot 1 lan 1 2 priority ipv6dscp

# Change the mapping of DSCP to operator priority:

#
# This example changes the mapping of DSCP 7, 15, 54, and 55
# to operator priority 1, 2, 7, and 7, respectively:
#

11/1543-HRA 901 17/7 Uen V | 2019-06-27 11

 Configuring Quality of Service (QoS)

end; config slot 1 lan 1 2 dscp-config dscp-decode 7 priority 1

end; config slot 1 lan 1 2 dscp-config dscp-decode 15 priority 2
end; config slot 1 lan 1 2 dscp-config dscp-decode 54 priority 7
end; config slot 1 lan 1 2 dscp-config dscp-decode 55 priority 7

3.1.3 Classifying and Marking Traffic Using PCP (CLI)

The valid values for PCP are 0–7. Table 4 shows the default mapping table for
PCP to operator priority.

Table 4 Default Mapping Table for PCP to Operator Priority

PCP Operator Priority
0 0
1 1
2 2
3 3
4 4
5 5
6 6
7 7

Example 3
# Set the customer priority classification:
#
# This example sets the priority classification to PCP (dot1p):
#
end; config slot 1 lan 1 2 priority dot1p

# Change the mapping of PCP to operator priority:

#
# This example changes the mapping of PCP 0, 3, and 6
# to operator priority 3, 2, 7 respectively:
end; config slot 1 lan 1 2 priority-config priority-map 0 mapped 3
end; config slot 1 lan 1 2 priority-config priority-map 3 mapped 2
end; config slot 1 lan 1 2 priority-config priority-map 6 mapped 7

3.1.4 Classifying and Marking Traffic using MPLS, DSCP, and PCP (CLI)

Example 4
# Set the customer priority classification:
#
# This example sets the customer priority classification
# to MPLS, DSCP, and PCP:

12 11/1543-HRA 901 17/7 Uen V | 2019-06-27

 CLI Configuration

#
end; config slot 1 lan 1 2 priority mplsIpDot1p

# Change the mapping of MPLS to operator priority:

#
# This example changes the mapping of MPLS TC 0, 1, and 5
# to operator priority 3, 4, and 7, respectively:
#
end; config slot 1 lan 1 2 mpls-exp-config mpls-exp-decode 0 priority 3
end; config slot 1 lan 1 2 mpls-exp-config mpls-exp-decode 1 priority 4
end; config slot 1 lan 1 2 mpls-exp-config mpls-exp-decode 5 priority 7

# Change the mapping of DSCP to operator priority:

#
# This example changes the mapping of DSCP 7, 15, 54, and 55
# to operator priority 1, 2, 7, and 7, respectively:
#
end; config slot 1 lan 1 2 dscp-config dscp-decode 7 priority 1
end; config slot 1 lan 1 2 dscp-config dscp-decode 15 priority 2
end; config slot 1 lan 1 2 dscp-config dscp-decode 54 priority 7
end; config slot 1 lan 1 2 dscp-config dscp-decode 55 priority 7

# Change the mapping of PCP to operator priority:

#
# This example changes the mapping of PCP 0, 3, and 6
# to operator priority 1, 2, 7 respectively:
end; config slot 1 lan 1 2 priority-config priority-map 0 mapped 1
end; config slot 1 lan 1 2 priority-config priority-map 3 mapped 2
end; config slot 1 lan 1 2 priority-config priority-map 6 mapped 7

3.1.5 Setting the Default Priority (CLI)

Example 5
# Set the default priority:
#
# This example sets the default priority to 6:
#
end; config slot 1 lan 1 2 priority-config default-priority 6

3.1.6 Mapping Operator Priority to Priority Queue (CLI)

Regardless of the selected type of classification (MPLS, DSCP, PCP, or a
combination), the mechanism for mapping operator priority to priority queue
uses one single mapping table. Configure this mapping table using the command
config cos dot1p priority-map-profile. Table 5 shows the default
mapping table for operator priority to priority queue.

11/1543-HRA 901 17/7 Uen V | 2019-06-27 13

 Configuring Quality of Service (QoS)

Table 5 Default Mapping Table for Operator Priority to Priority Queue

Operator Priority Priority Queue (Traffic Class)
0 1
1 0
2 2
3 3
4 4
5 5
6 6
7 7

It is also possible to create a customized mapping.

Example 6
# Create a customized mapping of operator priority to priority queue:
#
# This example defines a operator priority-to-priority queue mapping table
# with the name "ingressPrioMap":
#
end; config cos dot1p priority-map-profile ingressPrioMap

# Change the operator priority to priority queue mapping table:

#
# This example maps operator priorities 0, 1, and 2 to priority queue 2,
# operator priorities 3, 4, and 5 to priority queue 5,
# and operator priorities 6 and 7 to priority queue 7:
#
end; config cos dot1p priority-map-profile ingressPrioMap \
priority-map 0 class 2
end; config cos dot1p priority-map-profile ingressPrioMap \
priority-map 1 class 2
end; config cos dot1p priority-map-profile ingressPrioMap \
priority-map 2 class 2
end; config cos dot1p priority-map-profile ingressPrioMap \
priority-map 3 class 5
end; config cos dot1p priority-map-profile ingressPrioMap \
priority-map 4 class 5
end; config cos dot1p priority-map-profile ingressPrioMap \
priority-map 5 class 5
end; config cos dot1p priority-map-profile ingressPrioMap \
priority-map 6 class 7
end; config cos dot1p priority-map-profile ingressPrioMap \
priority-map 7 class 7

# Apply the operator priority-to-priority queue mapping table to the port:

#

14 11/1543-HRA 901 17/7 Uen V | 2019-06-27

 CLI Configuration

# This example applies the operator priority-to-priority queue mapping table

# with the name "ingressPrioMap" to the LAN port:
#
end; config slot 1 lan 1 2 cos priority-map-profile \
priority-map-profile ingressPrioMap

3.2 Configuring Queuing with WRED (CLI)

Note: It is not possible to modify a queue profile that is currently applied to a
port.

Example 7
# Create a new queue profile:
#
# This example creates a queue profile with the name "MyProfile:
#
end; config cos queue-profile MyProfile
#
# Configure the congestion control method for the queues:
#
# This example configures all queues in the profile "MyProfile" to use WRED:
#
end; config cos queue-profile MyProfile queue 0 congestion wred
end; config cos queue-profile MyProfile queue 1 congestion wred
end; config cos queue-profile MyProfile queue 2 congestion wred
end; config cos queue-profile MyProfile queue 3 congestion wred
end; config cos queue-profile MyProfile queue 4 congestion wred
end; config cos queue-profile MyProfile queue 5 congestion wred
end; config cos queue-profile MyProfile queue 6 congestion wred
end; config cos queue-profile MyProfile queue 7 congestion wred
#
# (optional) Add specific thresholds for active wred-range, per color.
# This example sets both thresholds for queue 0
# to 10 and 90 for both green and yellow traffic.
# If no thresholds are given, the thresholds are set to the default values (25,8 →
0).
#
end; config cos queue-profile MyProfile queue 0 congestion wred \
green-low-threshold 10 green-high-threshold 90 \
yellow-low-threshold 10 yellow-high-threshold 90
#
#
#
#
# (optional) Set the gain.
# The gain controls how quickly the average queue-size
# changes, and can be set from 0 to 15.
# If no value is given, the gain is set to default (0).
#
#

11/1543-HRA 901 17/7 Uen V | 2019-06-27 15

 Configuring Quality of Service (QoS)

end; config cos queue-profile MyProfile queue 0 congestion wred

exponent-weight 7
#
#
#
#
# (optional) Set the p-value.
# The p-value is the maximum drop probability,
# that is, the drop probability at the high threshold.
# This example sets p-values to 50 [%] and 75 [%]
# for green and yellow traffic.
#
#
end; config cos queue-profile MyProfile queue 0 congestion wred green-p-mark 5 →
0 yellow-p-mark 75
#
#
# Apply the profile to the port:
#
# This example applies the queue-profile "MyProfile" on the WAN port:
#
end; config slot 1 wan 1 5 cos queue-profile queue-profile MyProfile

3.3 Configuring Scheduling

The scheduling mechanism supports Strict Priority (SP), Weighted Fair Queuing
(WFQ), and combinations of SP and WFQ to empty the priority queues. Configure
this mechanism by selecting a scheduling profile. Table 6 shows both the order in
which the scheduling mechanism empties the priority queues and the default
mapping of priority queue to weight, depending on the selected scheduling
profile.

Table 6 config Overview of Scheduling Profiles

Scheduling Profile - Priority Queue Default Mapping of Priority Queue to
Emptying Order Weight
sp2-wfq6 01
2 high-priority SP queues 12
6 WFQ queues 23
34
45
56
60
70
sp3-wfq4-be 00

16 11/1543-HRA 901 17/7 Uen V | 2019-06-27

 CLI Configuration

Scheduling Profile - Priority Queue Default Mapping of Priority Queue to

Emptying Order Weight
3 high-priority SP queues 11
4 WFQ queues 22
1 low-priority SP queue - according to 33
best effort
44
50
60
70
sp3-wfq5 01
3 high-priority SP queues 12
5 WFQ queues 23
34
45
50
60
70
sp4-wfq3-be 00
4 high-priority SP queues 11
3 WFQ queues 22
1 low-priority SP queue - according to 33
best effort
40
50
60
70
sp8 N/A
8 SP queues
wfq8 01
8 WFQ queues 12
23
34
45
56
67

11/1543-HRA 901 17/7 Uen V | 2019-06-27 17

 Configuring Quality of Service (QoS)

Scheduling Profile - Priority Queue Default Mapping of Priority Queue to

Emptying Order Weight
78

3.3.1 Configuring Scheduling for Strict Priority (CLI)

Example 8
# Change the scheduling profile:
#
end; config cos scheduling profile sp8

3.3.2 Configuring Scheduling for Weighted Fair Queuing (CLI)

Example 9
# Change the scheduling profile:
#
end; config cos scheduling profile wfq8

# Configure the WFQ weights of the queues:

#
# This example configures the WFQ weights of all queues with decreasing
# weights. The total weight sum is 39 and the allocated bandwidth in
# percentage for each queue is calculated like this:
#
# Queue Weight Percentage
# ----- ------ -----------------
# 7 10 25.6% (10/39*100)
# 6 8 20.5% (8/39*100)
# 5 6 15.4% (6/39*100)
# 4 5 12.8% (5/39*100)
# 3 4 10.3% (4/39*100)
# 2 3 7.7% (3/39*100)
# 1 2 5.1% (2/39*100)
# 0 1 2.6% (1/39*100)
#
end, config cos scheduling config 7 weight 10
end; config cos scheduling config 6 weight 8
end; config cos scheduling config 5 weight 6
end; config cos scheduling config 4 weight 5
end; config cos scheduling config 3 weight 4
end; config cos scheduling config 2 weight 3
end; config cos scheduling config 1 weight 2
end; config cos scheduling config 0 weight 1

18 11/1543-HRA 901 17/7 Uen V | 2019-06-27

 CLI Configuration

3.3.3 Configuring Scheduling for a Mix of Strict Priority and Weighted Fair
Queuing (CLI)

Example 10
# Change the scheduling profile:
#
# This example changes the scheduling profile for classes 5 to 7
# to use strict priority, and classes 0 to 4 to use WFQ:
#
end; config cos scheduling profile sp3-wfq5

# Configure the WFQ weights of the queues:

#
# This example configures the WFQ weights of the WFQ queues with decreasing
# weights. The total weight sum is 15 and the allocated bandwidth in
# percentage for each queue is calculated like this:
#
# Queue Weight Percentage
# ----- ------ ----------------
# 4 5 33.3% (5/15*100)
# 3 4 26.7% (4/15*100)
# 2 3 20.0% (3/15*100)
# 1 2 13.3% (2/15*100)
# 0 1 6.7% (1/15*100)
#
end; config cos scheduling config 4 weight 5
end; config cos scheduling config 3 weight 4
end; config cos scheduling config 2 weight 3
end; config cos scheduling config 1 weight 2
end; config cos scheduling config 0 weight 1

3.4 Configuring Shaping (CLI)

Example 11
# Enable shaping on the LAN port or the WAN port and set the shaping rate:
#
# This example enables shaping on the LAN port and sets the shaping rate to
# 300 Mbps:
#
end; config slot 1 lan 1 2 shaping enabled shaping-rate 300000

3.5 Setting the Frame Size (CLI)

The system supports frames with a size up to 9,216 bytes (Jumbo Frames).

Example 12
# Set the MTU size:
#

11/1543-HRA 901 17/7 Uen V | 2019-06-27 19

 Configuring Quality of Service (QoS)

# This example sets the MTU size to 3000 bytes:

#
end; config slot 1 lan 1 2 lan-setting mtu 3000

20 11/1543-HRA 901 17/7 Uen V | 2019-06-27

 Node GUI Configuration

4 Node GUI Configuration

4.1 Configuring Scheduling

The scheduling mechanism supports Strict Priority (SP), Weighted Fair Queuing
(WFQ), and combinations of SP and WFQ to empty the priority queues. Configure
this mechanism by selecting a scheduling profile. Table 6 shows both the order in
which the scheduling mechanism empties the priority queues and the default
mapping of priority queue to weight, depending on the selected scheduling
profile.

Table 6 config Overview of Scheduling Profiles

Scheduling Profile - Priority Queue Default Mapping of Priority Queue to
Emptying Order Weight
sp2-wfq6 01
2 high-priority SP queues 12
6 WFQ queues 23
34
45
56
60
70
sp3-wfq4-be 00
3 high-priority SP queues 11
4 WFQ queues 22
1 low-priority SP queue - according to 33
best effort
44
50
60
70
sp3-wfq5 01
3 high-priority SP queues 12
5 WFQ queues 23
34
45

11/1543-HRA 901 17/7 Uen V | 2019-06-27 21

 Configuring Quality of Service (QoS)

Scheduling Profile - Priority Queue Default Mapping of Priority Queue to

Emptying Order Weight
50
60
70
sp4-wfq3-be 00
4 high-priority SP queues 11
3 WFQ queues 22
1 low-priority SP queue - according to 33
best effort
40
50
60
70
sp8 N/A
8 SP queues
wfq8 01
8 WFQ queues 12
23
34
45
56
67
78

4.1.1 Configuring Scheduling for Strict Priority (GUI)

To configure scheduling for strict priority:

Steps

1. Log on to the Node GUI (for information about accessing the Node GUI, see
Accessing a Network Element). The Overview page opens.

2. In the menu on the left, click Scheduling

3. Select 8 Strict Priority from the Profile drop-down list.

22 11/1543-HRA 901 17/7 Uen V | 2019-06-27

 Node GUI Configuration

4. Click Save.

4.1.2 Configuring Scheduling for Weighted Fair Queuing (GUI)

To configure scheduling for weighted fair queuing:

Steps

1. Log on to the Node GUI (for information about accessing the Node GUI, see
Accessing a Network Element). The Overview page opens.

2. In the menu on the left, click Scheduling

3. Select 8 WFQ from the Profile drop-down list.

11/1543-HRA 901 17/7 Uen V | 2019-06-27 23

 Configuring Quality of Service (QoS)

4. Set the desired Weight for each queue.

5. Click Save.

4.1.3 Configuring Scheduling for a Mix of Strict Priority and Weighted Fair
Queueing (GUI)

To configure scheduling for a mix of strict priority and weighted fair queuing:

Steps

1. Log on to the Node GUI (for information about accessing the Node GUI, see
Accessing a Network Element). The Overview page opens.

24 11/1543-HRA 901 17/7 Uen V | 2019-06-27

 Node GUI Configuration

2. In the menu on the left, click Scheduling

3. Select 3 strict priority + 5 WFQ from the Profile drop-down list.

4. Set the desired Weight for each weighted queue.

5. Click Save.

11/1543-HRA 901 17/7 Uen V | 2019-06-27 25