Back to Lab Listing

Lab Objective:

The objective of this lab exercise is for you to learn how to implement QoS functionality on a Cisco router.

Lab Purpose:

QoS is a networking strategy that allows for the management of the data traffic that traverses your network, to maintain a desired level of performance. QoS can guarantee the usual transmission of vital business traffic when the network is congested or overloaded. In this lab, you will configure classification to implement QoS. R2 will be a telnet server and R1 will act as telnet client. You will classify the telnet packets when they reach to R2 from R1.

Lab Tool:

Packet Tracer.

Lab Topology:

Please use the following topology to complete this lab exercise.

implementing quality of service (qos)

Lab Walkthrough:

Task 1:

Configure hostnames on R1 and R2 as illustrated in the topology.

Router#configure terminal

Router(config)#hostname R1

R1(config)#

 

Router#configure terminal

Router(config)#hostname R2

R2(config)#

Task 2:

Configure the IP addresses on the Gig0/0 interfaces of R1 and R2 as illustrated in the topology.

R1#configure terminal

R1(config)#interface gi0/0

R1(config-if)#ip address 192.168.10.1 255.255.255.0

 

R2#configure terminal

R2(config)#interface gi0/0

R2(config-if)#ip address 192.168.10.2 255.255.255.0

Task 3:

Connect to R2 and configure an access list named ACL_TELNET that matches telnet traffic.

R2#configure terminal

R2(config)#ip access-list extended TELNET_ACL

R2(config-ext-nacl)#permit tcp any any eq 23

Task 4:

On R2, configure a class-map where quality of service action is configured, and ACL from Task 3 is matched.

R2#configure terminal

R2(config)#class-map MATCH_TELNET

R2(config-cmap)#match access-group name TELNET_ACL

Task 5:

Next, create a policy map. Match the class map created from Task 4 and apply it under the interface. Use the following command to verify the policy-map applied to the interface.

show policy-map interface gi0/0

R2#configure terminal

R2(config)#policy-map CLASSIFY_TELNET

R2(config-pmap)#class MATCH_TELNET

R2(config-pmap)#exit

R2(config)#interface gi0/0

R2(config-if)#service-policy input CLASSIFY_TELNET

R2(config-if)#end

 

R2#show policy-map interface gi0/0

GigabitEthernet0/0

 

Service-policy input: CLASSIFY_TELNET

 

Class-map: MATCH_TELNET (match-all)

0 packets, 0 bytes

5 minute offered rate 0 bps, drop rate 0 bps

Match: access-group name TELNET_ACL

 

Class-map: class-default (match-any)

0 packets, 0 bytes

5 minute offered rate 0 bps, drop rate 0 bps

Match: any

Task 6:

Generate telnet traffic from R1 and verify the policy-map on R2 using the following commands.

show policy-map interface gi0/0

You can optionally enable telnet on R2, but the traffic will be classified either way.

R2(config)#line vty 0 15
R2(config-line)#password hello
R2(config-line)#login

R1#telnet 192.168.10.2

Trying 192.168.10.2 …Open

[Connection to 192.168.10.2 closed by foreign host]

R1#

 

R2#show policy-map interface gi0/0

GigabitEthernet0/0

 

Service-policy input: CLASSIFY_TELNET

 

Class-map: MATCH_TELNET (match-all)

3 packets, 124 bytes

5 minute offered rate 6 bps, drop rate 0 bps

Match: access-group name TELNET_ACL

 

Class-map: class-default (match-any)

4 packets, 991 bytes

5 minute offered rate 23 bps, drop rate 0 bps

Match: any

Notes:

This lab was very basic. You can configure QoS to trust certain interfaces, allocate bandwidth, and more.

Newsletter Subscribe

Stay Informed, Stay Inspired: Subscribe for Cutting-Edge IT-Certification Insights

101 Labs Newsletter