QoS on the IHUB

Objective

After completing this section, you’ll be able to …

 explain QoS on the IHUB
 describe each step of QoS on the services and ports:
• QoS Ingress and Egress Policies

• Egress Rate Limiting and Buffer Admission

• Port Egress Queue Policy

• Forwarding Classes (FCs) to Queue Mapping

• Self Generated Policy

 configure and retrieve QoS parameters on the IHUB using:

• AMS

• CLI
 QoS on the IHUB – General
Fixed Egress
Ingress QOS Switch to
Port Queue
Policy Egress Port
Policy

Service Map Packet Apply /Service Egress Priority Map FC Buffer Acceptance Port Egress
Lookup To FC Egress Rate Limit mapping To Queue & Scheduling Rate Limiter

Egress QoS Policy

The following QoS features are supported in the IHub switch hardware:

•Mapping packets to a flow class

•Per VPLS/VPRN/IES service egress rate limitation
•Mapping of flow classes to egress queues
pbit  EXP (if MPLS scenario) Queue

•Buffer acceptance and scheduling at egress port side

•Per-port egress rate limitation
3
1 QoS Ingress and Egress Policies

4
 Forwarding Classes (FCs)
 FCs serve to aggregate group of flows with similar loss, latency, jitter and bandwidth
characteristics from many user traffic flows

 Provides network elements with a method to weigh relative importance of one packet in
relation to another

• Determines how the packet is queued and handled

Network Control

High 1 U
S
Expedited SAP E
R

(FCs)
High 2

Low 1 T
R
Assured SDP A
F
Low 2 F
I
BEST EFFORT C

5
SERVICE
 QoS Ingress Policies – Which FC will be selected?

QoS Ingress Policies

 are applied to Services (VPLS – IES- VPRN)
 Map packets ingressing from SAPs/SDPs to forwarding classes (FCs)
 Classify each packet as in-profile or out-of-profile
QoS Ingress Access
/ Network Policy

Network Control

High 1 U
S
Expedited SAP E
R

(FCs)
High 2

Low 1 T
R
Assured SDP A
F
Low 2 F
I
BEST EFFORT C

6
SERVICE
 QoS Ingress Access Policy – How does it map?

Untagged-Frames:
 The default dot1p marking will be used for selecting the forwarding class

Pre-marked Packets
 If DSCP, IP Precedence and dot1p criteria defined then they will be evaluated in
the following order

1. DSCP

2. IP Precedence

3. Dot1p

 If no match is found on the packet, then the default FC (best effort) is used

The in/out-of-profile markings will be used in the Weighted Random Early

Discard (WRED) buffer acceptance algorithm used with egress queuing

7
QoS Ingress Access Policy – FC Selection Example

Rule 1) DSCP 36 ->“High 2” FC and Profile “In”

Rule 2) p-bit= 3 is ->“Low 1” FC and Profile
“Out”
Rule 3) p-bit= 0 is ->“BE” FC and Profile “Out”
Else
Default FC and Profile -> “BE” and “Out”
Network Control Default p-bit = 0

High 1

Expedited 1-) DSCP = 36

High 2 2-) p-bit =3

Low 1 SAP
3-) DSCP = 36, p-bit =3
Assured
4-) un-marked (untagged) Packet
Low 2

BEST EFFORT As the packet is untagged,

default p-bit setting will
Ingress
(FCs)
be applied
QoS Policy
8
 QoS Ingress Network Policy – How does it map?

 Defines the mapping of traffic ingressing from SDP bindings to FCs

• The classification can be based on:

o Experimental bits of the inner label (VC-label) or
o Priority bits of the encapsulated L2 frame, when present
• The mapping of packets to FCs based on DSCP and ToS is not supported
 In case a policy comprises both EXP and dot1p classification criteria then the EXP
classification takes precedence, except when the policy explicitly indicates to use the
inner p-bits
• Ether  a VLAN tag still needs to be added to the encapsulated packet before
sending it downstream. The setting of the priority bits for this added VLAN-tag is
based on the forwarding class which was applied as per the network ingress QOS
policy
• VLAN  the P-bits of the encapsulated packet are passed transparently

 If no match is found on the packet, then the default forwarding class is selected

9
 QoS Egress Network Policy

 The Label Switching Routers in the MPLS network use the experimental (EXP) bits of
the outer label to define the QoS handling. Therefore the ISAM offers the possibility
to configure the setting of these EXP bits
• A new policy where EXP value is derived from the FCs
o If a new policy is not defined, the default policy will be used by the service

 When the traffic received from SAPs is classified and about to be forwarded on the
Pseudo Wire (SDP), the packet is handled as follows:
• The EXP bits of the inner label will be derived from the FC and in/out profile, based on the
QoS Egress Network Policy

• The EXP bits of the outer label will be set to the same value as the inner label in the
Pseudo-Wire

• When the network interface is defined as a tagged interface, the priority bits of the outer
VLAN tag are derived from the EXP bits. This mapping is fixed (See notes)

10
Marking the frames from SAPs?
SAP TO SAP

- If the frame is pre-marked, it is sent

unchanged on another SAP. (FIXED PROFILE!)
SAP
P-bit=5 Service P-bit=5
SAP
SAP

- If the frame is untagged, the default P-bit=0

marking defined by ingress access policy will
be applied

SAP TO SDP

- The EXP bits marking will be set by the

Egress Network Policy based on the FC SAP
Service
-See Egress Network Policy on
SAP SDP
previous slide!

11
QoS Egress Network Policy – LSP EXP Marking Example
IN PROFILE FLOW OUT PROFILE FLOW

SERVICE Rule 1) @FC = BE -> In = 2 , Out = 0

Rule 2) @FC = Low 2 -> In = 1 , Out = 1

Rule 3) @FC = High1 -> In = 6 , Out = 5

NETWORK CONTROL
Else

HIGH 1 Default Profile -> will be applied

EXPEDITED

HIGH 2

LOW 1
SDP - LSP EXP =2

- LSP EXP =0
ASSURED

LOW 2

BE
(FCs) Egress
QoS Policy
12
2 Egress Rate Limiting,
Mapping (Queuing) and Buffer Admission

13
 Egress Rate Limiting Per Service

The rate limiter:

 Supported per VPLS and per VPRN/IES
 A VPRN rate limit has priority over a VPLS rate limit
 Applies to the traffic egressing on regular ports (network ports)
 Metering is two rate, three color and color aware. The metering will then update
the color. The color marking shall be used for egress queuing and WRED (to
discard low priority packets)

The following can be configured:

• CIR (Committed Information Rate)
• PIR (Peak Information Rate)
• CBS (Committed Burst Size)
• PBS (Peak Burst Size)

14
 Egress Rate Limiting Per Service/Port – Color Marking

 From the (default) service ingress QoS policy, all frames/packets

already get a color:
• Green for in-profile frames/packets
• Yellow for out-of-profile frames/packets
• Red can not be the result of an ingress policy
The service egress rate limiter will update this color, based on the metering
information
! Not all transitions are allowed:

15
 Egress Rate Limiting – What happens to “Green Packets”?
Rate
PBS

CBS
RED

PIR

YELLOW
YELLOW

CIR

GREEN GREEN GREEN GREEN

time
1- Profile IN/OUT packets were colored green/yellow at FC selection due to applied Ingress QoS Policy
2- Coloring is Traffic Rate dependent and is used to identify which packet will be dropped first. Not only in
case of congestion but also during limitation of the rate itself
3- The color of the packet/frame can be changed in these cases

16
FC to Queue Mapping

 What? The mapping of forwarding classes to egress queues

 The mapping policy is applied system-wide
 R3.7.10/R4.0.02  the forwarding class to egress queue policy cannot be
configured instead a default policy applies

17
 Egress Queuing
 The QoS policy that determines the order in which egress queues are served
 Egress queue policies are applied per port
 In ISAM R3.7.10/R4.0.02, the egress queue policy cannot be configured instead
a default policy applies to all ports

Network Control
High 1
Expedited
High 2
Low 1
Assured
(FCs)
Low 2
BEST EFFORT

The characteristics of this default egress queue policy are:

 4 egress queues per port

 Weighted Random Early Discard (WRED) is applied to all TCP IP packets

 Tail Drop for non-TCP (e.g. UDP) traffic

18
 Buffer Admission
 The queue parameters can not be changed in R.4.0.02
 For tail drop we have one parameter per color
• maximum queue size
 For WRED we have three parameters per color
• start average queue filling level
• maximum average queue filling level
• maximum drop probability
 The algorithm to accept or discard the packets into the egress queue is based on:
• The color of the frame: green, yellow or red
• The queue filling level

19
 Egress Scheduling

(FCs)
Network Control
High 1
Expedited
High 2
Low 1
Assured
Low 2
BEST EFFORT

The characteristics of this default egress scheduling:

 4 egress queues per port

 Round Robin scheduling over queue 1 and 0

 Strict Priority over queues 2 and 3

20
 Egress Rate Limiting Per Port - Shaping

The egress rate limiting per port is also possible at port level.
The following can be configured:
• Rate
• Burst Size (optionally, by default 256MB)

21
3 Self Generated Policies (SGTs)

22
 Self Generated QoS Policy

 What?  a QoS policy to define the DSCP value and dot1P bits for traffic
that is originated from the CPU of the NANT-D board
the default service SGT QoS policy 1 is applied by default:
DSCP = NC2
dot1P = 7
EXP = 7

23
4 Configuring QoS on the IHUB

24
QoS Ingress Access Policy – Create - AMS (1/2)

Network

Select NE

Infrastructure

QoS

QoS Ingress Access Policy

Create

QoS Ingress Access Policy

25
 QoS Ingress Access Policy – Create - AMS (2/2)

Network
Scope:
Template / Exclusive

Select NE

Infrastructure

QoS

QoS Ingress Access Policy the default-action to

desired values
Create

QoS Ingress Access Policy

In: Green
the default p-bits value for
Out: Yellow untagged frames

26
 QoS Ingress Access Policy – Create Rule - AMS (1/2)

Network

Select NE

Infrastructure

QoS

QoS Ingress
Access Policy
Add a FC and profile for a specific
QoS Ingress dot1p value
Access Policy # Create RULE: A received packet with a
p-bit 1 marking will select FC “Low1”
802.1p and will be marked as “Green”.

Create

QoS Ingress Access 802.1p

27
 QoS Ingress Access Policy – Create Rule - AMS (2/2)

Network

Select NE

Infrastructure

QoS
Add a FC and profile for a specific
dot1p value
QoS Ingress
Create RULE: A received packet
Access Policy with a p-bit 1 marking will select FC
“Low1” and will be marked as
QoS Ingress “Green” (In Profile = Green).

Access Policy #

802.1p

Create

QoS Ingress Access 802.1p

28
 QoS Ingress Access Policy – Apply to Service - AMS

Network

Select NE

Infrastructure

Layer 2/3

L2 Services/ L3 Services

29
 QoS Ingress Access Policy - CLI

1 Create a policy:
configure qos-servicerouter service-ingress 10 create
2 Modify the default-action to desired values:
configure qos-servicerouter service-ingress 10 default-action fc be profile in
3 Add a FC and profile for a specific dot1p value:
configure qos-servicerouter service-ingress 10 dot1p 5 fc ef profile in
4 Configure the default p-bits value for untagged frames
configure qos-servicerouter service-ingress 10 untagged-dot1p 4
5 The following command associates ingress QoS policy 10 to VPLS service 5:
configure service vpls 5 ingress qos 10

30
 QoS Ingress Policy – CLI - Show

show qos-servicerouter service-ingress <policy_ID>

show qos-servicerouter service-ingress “ALL” QoS Ingress

Policies

31
 QoS Ingress Network Policy – Create - AMS (1/2)

Network

Select NE

Infrastructure

QoS

QoS Ingress
Network Policy

Create

QoS Ingress Network Policy

32
 QoS Ingress Network Policy – Create - AMS (2/2)

Network
Scope:
Template / Exclusive
Select NE

Infrastructure

QoS

QoS Ingress
the default-action to
Network Policy desired values

Create

QoS Ingress Network Policy

In: Green
the default p-bits value for
Out: Yellow untagged frames

33
 QoS Ingress Network Policy – Create Rule - AMS (1/2)

Network

Select NE

Infrastructure

QoS

QoS Ingress
Network Policy
QoS Ingress
Network Policy #
LSP ExP

Create

QoS Ingress Network LSP EXP

34
QoS Ingress Network Policy – Create Rule - AMS (2/2)

Network

Select NE

Infrastructure

QoS

QoS Ingress
Network Policy
QoS Ingress
Network Policy #
LSP EXP

Create

QoS Ingress Network LSP EXP

35
QoS Ingress Network Policy – Apply to Service - AMS

Network

Select NE

Infrastructure

Layer 2

L2 Services

36
 QoS Ingress Network Policy - CLI

1 Create a policy:
configure qos-servicerouter service-ingress-network 4 create
2 Modify the default-action to desired values:
configure qos-servicerouter service-ingress-network 4 default-action fc
be profile out
3 Add a FC and profile for a specific lsp-exp value:
configure qos-servicerouter service-ingress-network 4 lsp-exp 3 fc "be"
profile "in“
4 The following command associates ingress QoS policy 10 to VPLS service
5:
configure service vpls 5 ingress-network qos 4

37
QoS Egress Network Policy – Create - AMS (1/2)

Network

Select NE

Infrastructure

QoS

QoS Egress
Network Policy

Create

QoS Egress Network Policy

38
 QoS Egress Network Policy – Create a FC Rule - AMS (2/2)

Network

Select NE

Infrastructure

QoS

QoS Egress
Network Policy

QoS Egress
Network Policy

Create

Forwarding Class

39
QoS Egress Network Policy – Apply to Service - AMS

Network

Select NE

Infrastructure

Layer 2

L2 Services

40
 QoS Egress Network Policy - CLI

1 Create a policy:
configure qos-servicerouter service-egress-network 3 create
2 Marking lsp-exp bits “Creating Rules based on forwarding classes”:
configure qos-servicerouter service-egress-network 3 fc "be" lsp-exp-in-
profile 3
3 The following command associates ingress QoS policy 10 to VPLS service 5:
configure service vpls 5 egress-network qos 3

41
Copy QoS Policies - CLI
configure qos-servicerouter copy ?

 - copy service-ingress <src-pol> <dst-pol> [overwrite]

 - copy service-ingress-network <src-pol> <dst-pol> [overwrite]

 - copy service-egress-network <src-pol> <dst-pol> [overwrite]

 - copy sgt <src-pol> <dst-pol> [overwrite]

 It is not allowed to copy a policy to an existing policy unless the overwrite keyword is specified.

- When the overwrite keyword is not specified, a new destination policy is created.

If you want to edit a policy that is currently in use, use the following procedure:

• 1 Copy the policy ID in use to an unused policy ID

• 2 Edit the copy “offline” as needed

• 3 Copy the unused policy ID back to the policy ID in use, while specifying the overwrite
keyword

42
Copy QoS Policies - AMS

Network

Select NE

Infrastructure

QoS

QoS Ingress
Access Policy

QoS Ingress
Access Policy #
It’s also possible to
Actions overwrite an existing one

Copy

43
 Egress Rate Limiting Per Service - AMS

equipment

Select NE

Infrastructure

Layer 2/Layer 3

L2 Services/L3 Services

44
Egress Rate Limiting Per Service - AMS

VPLS SERVICE VPRN SERVICE IES SERVICE

Network Network Network

Select NE Select NE Select NE

Infrastructure Infrastructure Infrastructure

Layer 2 Layer 3 Layer 3

L2 Services Layer 3 Services Layer 3 Services

VPLS Service # Service # (VPRN ) Service # (IES )

47
 Egress Rate Limiting Per Port - AMS

equipment

Select NE

SLOT NT

Ethernet Port #

48
Egress Rate Limiting Conf. on Services and Ports - CLI

1 Egress Rate Limiting on Service:

configure service vpls/vprn/ies <VPLS/VPRN/ies_ID> egress rate-limit
cir <rate-in-kbps> pir <rate-in-kbps> [cbs <size-in-kbytes>] [pbs <size-
in-kbytes>]
<rate-in-kbps> : [0...10000000|max]
<rate-in-kbps> : [1...10000000|max]
<size-in-kbytes> : [1...262144|default]
<size-in-kbytes> : [1...262144|default]

2 Egress Rate Limiting on the port:

configure port <port_id> ethernet egress-rate <sub-rate> burst
<burst-size>
<sub-rate> : [1...10000000] - kbps
<burst size> : [1...262144|default] - KBytes

49
Egress Rate Limiting on Port– CLI - Show

show port <port_ID> [detail]

50
 Egress Rate Limiting – CLI - Show

show service id <service_id> all

51
Self Generated Policy – Create - AMS (1/2)

Network

Select NE

Infrastructure

QoS

QoS
Self-Generated Policy

52
 Self Generated Policy – Create - AMS (2/2)

Network

Select NE

Infrastructure

QoS

QoS
Self-Generated Policy

53
 Self Generated Policy– Apply to Service - AMS

Network

Select NE

Infrastructure

Layer 2/Layer 3

L2 Services/L3 Services

54
Self Generated Policy - CLI

1 Create a self-generated traffic policy:

configure qos-servicerouter sgt <sg_policy_id> default-dscp <dscp_#> default-
dot-1p <dot1p_#> default-lsp-exp <lsp_exp_#> scope exclusive
2 Apply to a service:
configure service vpls/ies/vprn <service_id> sgt-qos <policy_id>

55
 Self Generated Policy – CLI - Show

show qos-servicerouter sgt <policy_ID>

show qos-servicerouter sgt “ALL” SGT Policies

56
The qos-using Command

show services qos-using [policy_id] {ingress|sgt}

57
 www.alcatel-lucent.com
www.alcatel-lucent.com

58