03814 Updated RevB

Exercises for IP QoS Fundamentals on SSR

Exercises

03814-Customized


- 2 - Ericsson AB 2014 03814-Customized

DISCLAIMER This document is a training document and contains simplifications. Therefore, it must not be considered as a specification of the system. The contents of this document are subject to revision without notice due to ongoing 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. This document is not intended to replace the technical documentation that was shipped with your system. Always refer to that technical documentation during operation and maintenance.

Ericsson AB 2014 This document was produced by Ericsson. The document is to be used for training purposes only and it is

strictly prohibited to copy, reproduce, disclose or distribute it in any manner without the express written consent from Ericsson.


03814-Customized Ericsson AB 2014 - 3 -

Exercise 1 Case 0; Building the topology This case allows you to create the topology for QoS policy Metering Lab using the steps listed below. We need to create two contexts, configure IP addresses, and bind the interface to the contexts.

The network topology reference used for this training is illustrated in the following logical diagram.

Diagram 1, Case 0: Reference for QoS policy Metering Lab

You are expected to perform the following:

Step 1:

Context configuration mode:

Create/configure context test Create interface gen and with IP address (see table

bellow)

Create interface test and with IP address (see table bellow)

Configure a static route from 0.0.0.0/0 to 1.1.1.1/2 Port configuration mode:

Exercises for QoS Fundamentals on SSR

- 4 - Ericsson AB 2014 03814-customized based LZU1088093 Rev A

For Ethernet port 3/12, no shut, configure a medium speed 100 full duplex and bind this port to interface gen on context test.

For Ethernet port 5/1, no shut and bind this port to interface test on context test

Context configuration mode:

Create/configure context dummy Configure interface subs loopback, with IP address

200.1.1.100/24

Configure interface test with IP 1.1.1.2/24 For Ethernet port 5/2, no shut and bind interface test to

context dummy

Summary:

Context Interfaces Port & Circuits

test gen, 100.1.1.x/24 where x = group number [15]

test, 1.1.1.1/24, ip route 0.0.0.0/0 1.1.1.2

3/12, no shut, medium speed 100 duplex full, bind int gen test

5/1, no shut, bind int test test

dummy subs loopback, ip address 200.1.1.100/24

test, ip address 1.1.1.2/24

Ethernet 5/2, no shut, bind int test dummy

Step 2: Verification After the topology configuration, proceed to verification and check the configuration using the commands:

show port show bind show ip interface ping 100.1.1.1 (traffic generator from context test) ping 1.1.1.2 (next hop for context test)



Step 3: Traffic forwarding: Verify the traffic generation and verify the traffic forwarding by configuring and then executing following macro:

This macro will be used throughout the course. Execute macro case-1 twice with at least 30 seconds interval.

Note the results: Port Traffic, kbps

3/12

5/1

5/2

macro exec case-0 seq 10 show clock seq 20 show port count 3/12 live | grep option '-E' 'bit|eth' seq 30 show port count 5/1 live | grep option '-E' 'bit|eth' seq 40 show port count 5/2 live | grep option '-E' 'bit|eth'



Exercise 2 Case 1; QoS Policy Metering The object is to configure QoS policy called case-1 for metering and enabling metering counters with the keyword counters.

Following is a general command template that you will use to configure the QoS metering policy case-1:

Diagram 1: QoS policy metering / policing (traffic agnostic)

Step 1: Configure QoS policy case-1 metering:

Global configuration mode: - Configure QoS policy case-1 metering, rate

metering 2000 burst 375000 counters (rate limit to 2 Mbps)

- Note! Do not use marking (it will be used later) - Note! Use the system default Exceed and

Confirm behavior Step 2: Apply policy to port 5/1

Port configuration mode: - For port ethernet 5/1, configure QoS policy

metering case-1



Summary:

Qos policy Port & Circuits

case 1 metering, rate 2000 burst 375000 counters 5/1, no shut, qos policy metering case-1

Step 3:

Verify QoS policy configuration and status using following commands:

show qos policy show qos policy metering case-1 show qos port slot 3

Step 4:

Verify overall traffic flow using case-0 macro:

Note the results:

Port Traffic, kbps

3/12

5/1

5/2

Step 5:

Configure new macro case-1 to analyze the results of applying QoS policy case-1 to port 5/1

Note the result: ____ kbps

macro exec case-1 seq 10 show clock seq 20 show circuit count 5/1 detail | grep option '-E -i'

'transmit\/sec|conf|exc'



Was there any congestion?



Exercise 3 Case2; QoS Policy Metering with Classes

Case-2 demonstrates the steps needed in order to implement QoS metering policy with classes. The following are the procedures to implement class-based QoS policy:

Step 1: Create Policy Access-list within context

Go to configuration mode for context test Configure a new policy access-list called case-2-acl Define different classes for each traffic type:

seq 10 to permit tcp from any tcp source to any tcp destination equal to www as class browsers

seq 20 permit tcp from any source to any destination equal to ftp as class ftp-stuff

seq 30 to permit ip traffic from any source to any destination as class unknown

Step 2: Create QoS policy on global level

Configure the qos policy case-2 for metering Configure access-group case-3-acl and associate

it to the ACL case-2-acl in context test. For each class define:

For class browsers, set rate to 2000 with burst 375000 counters

For class ftp-stuff, set rate to 10000 with burst 375000 counters

For class unknown, set rate to 500 with burst 1000 counters



Step 3: Apply QoS policy to egress port 5/1:

Enter port configuration mode for port ethernet 5/1, no shut

Remove old policy first (no qos policy metering case-1)

Configure qos policy policing metering case-2

Summary:

Context ACL policy Port & Circuits

test access-list case-2-acl

seq 10 permit tcp any any eq www class browsers

seq 20 permit tcp any any eq ftp class ftp-stuff

seq 30 permit ip any any class unknown

5/1, no shut, bind int test test, qos policy metering case-2

qos policy access-group classes

case-2 metering

case-2-acl test

browsers, rate 2000 burst 375000

ftp-stuff, rate 1000 burst 10000 counters

unknown, rate 500 burst 1000 counters

Port & Circuits

5/1, no shut, bind int test test

Step 4: Verify the QoS policy: Show configuration qos Show qos policy metering Show qos policy metering case-2 Show qos port slot 5



Step 5: verify overall traffic with macro case-0


3/12

5/1

5/2

What is the total expected traffic rate? _____ kbps Is the total traffic what you expected?

To explain the possible deviation between expected rate and simulation results we have to look at more detailed counters.

Step 6: configure following macro to be used for analyzing conforming / exceeding traffic with classes for case-2:

Note the results: Port 5/1, Classes

Configured rate, kbps

Confirmed traffic rate: kbps / %

browsers

ftp-stuff

unknown

Total

Which class(s) has difference(s) from expected rates?

macro exec case-2 seq 10 show clock seq 20 show circuit count 5/1 detail | grep option '-E -i'

'transmit\/sec|conf|exc|class'



Step 7: Calculate the correct burst values for class ftp-stuff and class unknown according to token bucket principle:

Classes Configured

rate, kbps Burst value to configure

browsers 2000

ftp-stuff 1000

unknown 500

Step 8: Step 8, Solution, Case-2: Calculate the correct burst values for class ftp-stuff and class unknown according to token bucket principle:

Step 9: Configure the burst values for classes according to your calculation above.

Step 10: Verify the new QoS policy: Show qos policy metering Show qos policy metering case-2 Show qos port slot 5 Show configuration qos

Step 11: verify overall traffic with macro case-0 Is the total rate as you expected?

Step 12: Again, execute macro case-2 twice with at least 30 seconds interval. The result should match expected rates per class.

Step 13: Verify the number of hits for the ACL (if counters are enabled) to check the ACL configuration:

show access-group qos 5/1 out count Note! You may need to enable the acl-counters for the QoS

policy in port configuration mode

This is used to verify the classification configured.

Burst = expected rate Tc Rule of thumb Tc = 1.5 s



Exercise 4 Queue Mapping Queue-maps are used to map each packet with priority value of internal packet descriptor (see bellow) to a specific queue. Following is a general template for configuration of customized queue-maps. You will use it to configure your own customized queue-map.

Diagram for queue mapping: customized queue mapping

Step 1: Configure customized Queue-map:

Define a new qos queue-map called only-4 in global configuration mode.

Assign the total number of queues to 4. Configure the queue-mapping as below:

Q0 will be used for packets with internal priority 0 Q1 will be used for packets with internal priority 1 Q2 will be used for packets with internal priority 2 Q3 will be used for any other traffic (internal priority

= 3..7)



Summary:

qos queue-map

num-queues queue and priority

only-4 4 queue 0 to priority 0

queue 1 to priority 1


queue 3 to priority 3 4 5 6 7

Step 2: Verification:

Verify you queue-map configuration: show qos queue-map show qos queue-map only-4



Priority Queuing (scheduling): Introducing congestion point

For priority queuing (scheduling) exercise, the following steps are to be implemented:

Classification of incoming traffic Marking packets with internal priority Mapping priorities into queues Scheduling (PQ)

Step 1: Configure port parameters to introduce congestion point:

First you need to introduce congestion in out test network setup. You will configure port 5/1 and 5/2 to introduce congestion. Please implement the traffic congestion condition according to the following:

Port / circuit configure with parameters

port ethernet 5/1, medium speed 10 duplex full

port ethernet 5/2, medium speed 10 duplex full

Step 2: Verify overall traffic with macro case-0:


3/12

5/1

5/2



Exercise 5 Case 3a: Setting internal priority per class

The following is the logical diagram displaying the configuration procedures to implement classification and setting the internal priority (marking) for each class.

Diagram 1, Case 3a: PQ scheduling

Step 1: Classify the traffic with ACL (use the above diagram):

Go to context test Configure a new policy access-list called case-3-acl Define different classes for each traffic type:






Step 2: Set the internal priority per class:

Configure a new qos policy called case-3 with policing Configure access-group associated to case-3-acl in

context test

For class browsers, mark with priority 1 For class ftp-stuff, mark with priority 0 For class unknown, mark with priority 3 Remember priority is the priority value in the internal packet descriptor.

Step 3: Apply QoS policy to ingress port

Enter configuration mode for port ethernet 3/12, no shut Bind interface gen to context test (should already be there) Configure qos policy policing case-3-classification with

acl-counters for this port

Summary:

context test qos policy

Port / circuit

policy access-list

case-3-acl,

seq 10 permit tcp any any eq www class browsers,

seq 20 permit tcp any any eq ftp class ftp-stuff,


case-3-classification policing

access-group case-3-acl test

class browsers, mark priority 1

class ftp-stuff, mark priority 0

class unknown, mark priority 3

port ethernet 3/12

no shut, bind interface gen to test

qos policy policing case-3 classification acl-counter

Step 4: Verify the configuration:



show access-group qos 3/12 in counters (enable the counters as you did before)

show qos policy policing show qos policy policing case-3-classification



Case 3a: PQ Scheduling Until now you have configured:

Classification of incoming traffic Marking packets with internal priority Mapping priorities into queues

This exercise outlines steps required to implement PQ scheduling according to the diagram bellow:

Create Queue map on global level (step 1 in the diagram) Create QoS policy on global level (step 2) Apply QoS policy on port or circuit level (step 3)

Diagram 2, Case 3a: PQ Scheduling

Step 1: Create Queue map on global level

Configure the qos queue-map called only-4 (should already be there)

Assign the total number of 4 queues with following priority values (should already be there):

Q0 will be used for the highest priority traffic with priority value 0 (IP precedence = 7)



Q1 will be used for the traffic with priority value 1 (IP precedence = 6)


Q3 will be used for any other traffic, priority value 3..7 (IP precedence = 0..4)


For qos policy called case-3 pwfq, assign the maximum rate to 100000, num-queues to 4, queue-map to only-4. For each queue use following settings:

queue 0 priority 0 weight 100 queue 1 priority 1 weight 100 queue 2 priority 2 weight 100 queue 3 priority 3 weight 100

Why do we use the same weight value 100 for all queues? Answer: ____________________________________

Step 3: Apply QoS policy on port or circuit level

Enter configuration mode of Ethernet port 5/1 and apply qos policy queuing case-3

Summary



qos queue-map

num-queues queue and internal priority

only-4

(use earlier config)

4 queue 0 to priority 0




qos policy num-queues parameters for PQ-scheduling

case-3 pwfq, rate maximum 100000

4 only-4

queue 0 to priority 0 with weight 100




port/circuit -

5/1 qos policy queuing case-3

Step 4: Verification of QoS policy for PQ

show the qos policy show qos policy for case-3

Step 5: Verify overall traffic with macro case-0: Note the results:

Port Traffic, kbps

3/12

5/1

5/2

Step 6: configure following macro to analyze scheduling configuration results:



Step 7: Execute macro case-3 twice with at least 30 seconds interval .Note and explain the result for each queue and the total traffic:

Queues Transmitted traffic rate, kbps

Explain result, Comments

Queue 0

Queue 1

Queue 2

Queue 3

Total

macro exec case-3 seq 10 show clock seq 20 show circuit counters 5/1 queue



Exercise 6 Case 3b: PQ with rate limiting This exercise introduces rate limiting with PQ which allows traffic in lower priority queues to be transmitted and avoid starvation during congestion. You will use procedures in the following reference diagram:

Diagram 1, Case 3b: Adding rate limit into PQ scheduler

Step 1: Create Queue map on global level (should already be there)

Configure the qos queue-map called only-4 Assign the total number of 4 queues with priority:








For qos policy called case-3 with pwfq, assign the maximum rate to 100000, num-queues to 4, queue-map to only-4.

For each queue use following settings (already done!): queue 0 priority 0 weight 100 queue 1 priority 1 weight 100 queue 2 priority 2 weight 100 queue 3 priority 3 weight 100

For each queue (= priority-group here) configure following rate

Priority-group 0: rate 2000 and with exceed option

Priority-group 1: rate 2000 Priority-group 2: rate 1000 Priority-group 3: rate 500

Step 3: Apply QoS policy on port/circuit level:

Enter configuration mode of Ethernet port 5/1 and apply qos policy queuing case-3

Summary:

qos queue-map

num-queues queue and internal priority

only-4

(use earlier config)

4 queue 0 to priority 0




qos policy num-queues parameters for PQ-scheduling




(change existing policy)

4 only-4





queue priority-group 0 rate 2000 exceed

queue priority-group 1 rate 2000



port/circuit -

5/1 qos policy queuing case-3

Step 4: Verify the PQ policy:

show qos policy pwfq case-3 clear the port counters before next step

Step 5: Verify the traffic flow:

Execute macro case-3 twice with at least 30 seconds interval.

Note and explain the result for each queue and the total traffic:



Queue 0

Queue 1

Queue 2

Queue 3

Total



Exercise 7 Case 3c: PQ combined with WRED In this exercise, WRED (Weighted Random Early Detection) congestion management will be added to PQ scheduling. Following figure shows the general configuration steps:

Diagram 1, Case 3c: Adding WRED into PQ scheduler

Perform the following steps to implement Case 3C:

Step 1: Create Queue map on global level (should already be there)

Configure the qos queue-map called only-4 Assign the total number of 4 queues with priority:





Step 2: Create Congestion Avoidance map on global level



Configure a qos-configuration-avoidance-map called case-3-WRED with pwfq

Assign queue 0 red default min-threshold 3000 max-threshold 4000 probability 1000




Configure/Enter qos policy case-3 as pwfq For qos policy case-3 pwfq, assign the maximum rate to

100000, num-queues to 4, queue-map to only-4, congestion-map case-3-WRED together with the following traffic queue priority:

queue 0 priority 0 weight 100 queue 1 priority 1 weight 100 queue 2 priority 2 weight 100 queue 3 priority 3 weight 100 queue priority-group 0 rate 2000 exceed

Step 4: Apply QoS policy on port or circuit level

For Ethernet port 5/1, apply qos policy queuing case-3

Summary:

qos queue-map

num-queues queue and priority

only-4 4 queue 0 to priority 0




qos congestion-avoidance-map queue-map



case-3-WRED pwfq queue 0 red default min-threshold 3000 max-threshold 4000 probability 1000

queue 1 red default min-threshold 2000 max-threshold 3000 probability 10

queue 3 red default min-threshold 1000 max-threshold 2500 probability 2

qos policy num-queues queue-map


4 only-4, congestion-map as case-3-WRED

queue 0 to priority 0 with weight 100,




qos policy num-queues queue-map


4 only-4





Port/Circuits

5/1 medium speed 10 duplex full, no shut, bind int test test, qos policy queuing case-3

Step 5: Verify the configuration and the results of QoS policy with WRED on traffic:

show qos policy pwfq case-3. clear port counters Execute macro case-3 twice with at least 30 seconds

interval. Note the results in following table:



Queues Bytes sent WRED drops Tail drops

Queue 0

Queue 1

Queue 2

Queue 3

Compare to tail drops from previous exercise.



Exercise 8 Case 4: Scheduling with WFQ In this exercise you will implement another scheduling method: Weighted Fair Queuing. When WFQ is enabled the available bandwidth is shared between the queues according to associated weights. Following is the general steps to configure WFQ:

Diagram 1, Case 4: traffic classification - class based policy

Step 1: Classify the traffic (already done!):

Go to context configuration mode for context test Configure policy access-list called case-3-acl Configure following classification for each traffic type:




Step 2: Set the internal priority per class (already done!):



Configure the qos policy case-3 policing Associate access-group to case-3-acl in context test For class browsers, mark priority 1 For class ftp-stuff, mark priority 0 For class unknown, mark priority 3

Step 3: Apply QoS policy to ingress traffic on port 3/12

Enter configuration for port ethernet 3/12 Apply qos policy policing case-3-classification acl-counters

Summary:

context policy access-list qos policy

Port / circuit

test case-3-acl,




case-3-classification policing with





port ethernet 3/12


qos policy policing case-3 classification acl-counter

Following diagram shows the general steps to configure WFQ:



Diagram 2, Case 4: WFQ Scheduling

Step 1-WFQ:

Configure qos queue-map only-4 (already done!) For each queue assign following internal priority values:

Q0 will be used for priority 0

Q1 will be used for priority 1

Q2 will be used for priority 2 Q3 will be used for any other traffic (priority = 3..7)

Step 2-WFQ: Configure QoS policy on global level:



For qos policy case-4 pwfq, assign the maximum rate to 100000, num-queues to 4, queue-map to only-4. Assign following weight values:

queue 0 to priority 0 with weight 15 queue 1 to priority 0 with weight 30 queue 2 to priority 0 with weight 5 queue 3 to priority 0 with weight 50

Step 3-WFQ: Apply QoS policy to port 5/1:

For ethernet port 5/1 apply qos policy queueing case-4

Step 4-WFQ: Verify the results of QoS policy WFQ:

show qos policy show the qos policy pwfq case-4 Execute macro case-0 and note the results:

Port Traffic, kbps

3/12

5/1

Summary:


Port / circuit

test case-4-acl,




case-3 pwfq

configure rate maximum 100000

num-queues 4, queue-map only-4

queue 0 priority 0 weight 15




port ethernet 5/1

configure medium speed 10 with duplex full, no shut, bind interface test to context test and qos policy queueing case-4



5/2

Step 5-WFQ: Verify the traffic:





Queue 0

Queue 1

Queue 2

Queue 3

Total



Exercise 9 Case 5: PWFQ Exercise The objective of this exercise is to combine PQ and WFQ to prioritize different traffic flows by separating them into different queues for the same destination. Same configurations from last exercise will be used including classification of incoming traffic, marking packets with internal priority, mapping priorities to queues.

Following diagram shows the configuration steps for PWFQ:

Diagram 1, Case 5: Traffic classification - class based policy

Step 1: Classify the traffic (already done!):

Go to configuration mode for context test Configure policy access-list case-3-acl Configure following classification for each traffic type:






Step 2: Configure the internal priority per class (already done!)

Configure the qos policy case-3 policing Associate access-group to case-3-acl in context

test

For class browsers, mark priority as 1 For class ftp-stuff, mark priority 0 For class unknown, mark priority 3

Step 3: Apply QoS policy to ingress port (already done!):

Configure port ethernet 3/12 Configure qos policy policing case-3-classification

as acl-counters

Summary:


Port / circuit

test case-3-acl,




case-3-classification policing with





port ethernet 3/12


qos policy policing case-3-classification acl-counter



Diagram 2, Case 5: PWFQ Scheduling

Step 1PWFQ:

Configure qos queue-map only-4 (already done!)

Step 2PWFQ: Configure QoS policy on global level:

For qos policy case-5 pwfq, assign the maximum rate to 100000, num-queues to 4, queue-map to only-4. Configure following PWFQ parameters:

queue 0 to priority 0 with weight 15 queue 1 to priority 0 with weight 40 queue 2 to priority 0 with weight 85 queue 3 to priority 0 with weight 60 queue priority-group 0 rate 2000



Step 3PWFQ: Apply QoS policy to port 5/1:

qos policy queueing case-5

Summary:


Port / circuit

test case-3-acl,




case-5 pwfq

configure rate maximum 100000

num-queues 4, queue-map only-4





port ethernet 5/1

configure medium speed 10 with duplex full, no shut, bind interface test to context test and qos policy queueing case-5

Step 4PWFQ: Verify the configuration and the results of QoS policy with PWFQ:

show qos policy show the qos policy pwfq case-5 Execute macro case-0 and note the results:

Port Traffic, kbps

3/12

5/1

5/2



Step 5PWFQ: Verify the traffic:



Queues Transmitted

traffic rate, kbps


Queue 0

Queue 1

Queue 2

Queue 3

Total

Documents

03814 Updated RevB