Lab 9.8.

1 Managing Network Performance Using Content-Based Weighted Fair

Queuing (CBWFQ) and Low Latency Queuing (LLQ)

Objective
Use an access list to define the traffic of interest that is to be classified and configure a class map
that associates the access list to a content class. Configure a policy map that associates a content
class to a queue and guarantees bandwidth. Configure class-based weighted fair queuing (CBWFQ)
on an interface and verify class-based weighted fair queuing operation.

Scenario
Users at the London office of the International Travel Agency (ITA) are reporting problems with traffic
coming from the SanJose1 site. HTTP packets are being dropped due to other network traffic that is
on the Frame Relay link. Users at the SanJose1 office have also been complaining that Telnet traffic
going to the London office is also being degraded.
After studying traffic patterns, ITA management has decided to allocate 50 percent of the available
Frame Relay bandwidth for HTTP network traffic going to the London office from the SanJose1 office
LAN connection. Another 25 percent of all network traffic traversing the Frame Relay link will be
allocated to Telnet traffic coming from the SanJose1 LAN connection. All other traffic will contend for
the remaining available Frame Relay bandwidth.
ITA has been decided to implement class-based weighted fair queuing (CBWFQ) to support the
management defined QoS requirements.

1-7

CCNP 2: Remote Access v 3.0 - Lab 9.8.1

Copyright 2003, Cisco Systems, Inc.

The Singapore site is directly connected to the London. The Singapore router will be used to
generate IP traffic to test the queuing on the Frame Relay connection. Three loopback interfaces will
be configured on the Singapore router for the extended ping tests.

Step 1
Before beginning this lab, it is recommended that each router be reloaded after erasing its startup
configuration. This prevents problems that may be caused by residual configurations. Cable the network
according to the diagram. This lab assumes an Adtran Atlas 550 will be used to emulate the Frame
Relay cloud. Be sure to connect the serial interfaces on the router to the port as labeled in the diagram.
On each router, configure their respective hostname and FastEthernet address.
On the SanJose1 router, configure the following:
SanJose1(config)#int s 0/0
SanJose1(config-if)#ip address 192.168.192.1 255.255.255.0
SanJose1(config-if)#encapsulation frame-relay
SanJose1(config-if)#frame-relay lmi-type ansi
SanJose1(config-if)#no shut

For convenience sake, configure a default route to London as follows:

SanJose1(config)#ip route 0.0.0.0 0.0.0.0 192.168.192.2

On the London router, configure the serial interfaces and static routes as follows:
London(config)#int s0/0
London(config-if)#ip address 192.168.192.2 255.255.255.0
London(config-if)#encapsulation frame-relay
London(config-if)#frame-relay lmi-type ansi
London(config-if)#no shut
London(config-if)#exit
London(config)#int s 0/1
London(config-if)#ip address 192.168.199.1 255.255.255.0
London(config-if)#no shut
London(config-if)#exit
London(config)#ip route 192.168.0.0 255.255.255.0 192.168.192.1
London(config)#ip route 192.168.232.0 255.255.248.0 192.168.199.2

On the Singapore router, configure the serial interface, enable password, Telnet services, loopback
interfaces and the default route as follows:
Singapore(config)#int s0/1
Singapore(config-if)#ip address 192.168.199.2 255.255.255.0
Singapore(config-if)#clock rate 56000
Singapore(config-if)#no shut
Singapore(config-if)#exit
Singapore(config)#interface lo 0
Singapore(config-if)#ip address 192.168.233.1 255.255.255.255
Singapore(config)#interface lo 1
Singapore(config-if)#ip address 192.168.234.1 255.255.255.255
Singapore(config)#interface lo 2
Singapore(config-if)#ip address 192.168.235.1 255.255.255.255
Singapore(config)#enable password cisco
Singapore(config)#line vty 0 4
Singapore(config)#password cisco
Singapore(config)#login
2-7

CCNP 2: Remote Access v 3.0 - Lab 9.8.1

Copyright 2003, Cisco Systems, Inc.

Singapore(config)#ip route 0.0.0.0 0.0.0.0 192.168.199.1

With the extended ping command, verify connectivity between the FastEthernet LAN on SanJose1
and the FastEthernet LAN and Loopback addresses on Singapore.w

Step 2
In this step, the class-map and policy-map for class-based weighted fair queuing will be configured
on the SanJose1 router. On the SanJose1 router, create an extended ip access list 100 to permit
HTTP traffic requests coming from the SanJose1 LAN network going to the London LAN network.
SanJose1(config)#access-list 100 permit tcp 192.168.0.0 0.0.0.255 192.168.200.0
0.0.0.255 eq www

Create another extended ip access list 101 to permit Telnet traffic requests originating from the
SanJose1 LAN network going to London LAN network.
SanJose1(config)#access-list 101 permit tcp 192.168.0.0 0.0.0.255 192.168.200.0
0.0.0.255 eq telnet

Create a class-map named HTTP-CLASS and configure a match condition with access list 100.
SanJose1(config)#class-map match-all HTTP-CLASS
SanJose1(config-cmap)#match access-group 100

Create a class-map named TELNET-CLASS and configure a match condition with access list 101.
SanJose1(config-cmap)#class-map match-all TELNET-CLASS
SanJose1(config-cmap)#match access-group 101
SanJose1(config-cmap)#exit

Create a policy-map named CBWFQ-CENTRAL. In the policy map, create a traffic policy for class
HTTP-CLASS to allocate a minimum of 50 percent of the available bandwidth. Under the same
policy map, create a traffic policy for class TELNET-CLASS allocating a minimum of 25 percent of
the available bandwidth.
SanJose1(config)#policy-map CBWFQ-CENTRAL
SanJose1(config-pmap)#class HTTP-CLASS
SanJose1(config-pmap-c)#bandwidth percent 50
SanJose1(config-pmap-c)#class TELNET-CLASS
SanJose1(config-pmap-c)#bandwidth percent 25
SanJose1(config-pmap-c)#exit

Create a Frame Relay traffic shaping map-class called TSLAB. Set the CIR to 9600, the traffic rate
to 9600, and the adaptive shaping to BECN. Finally apply the service policy CBWFQ-CENTRAL as
follows:
SanJose1(config)#map-class frame-relay TSLAB
SanJose1(config-map-class)#frame-relay cir 9600
SanJose1(config-map-class)#frame-relay traffic-rate 9600 9600
SanJose1(config-map-class)#frame-relay adaptive-shaping becn
SanJose1(config-map-class)#service-policy output CBWFQ-CENTRAL
SanJose1(config-map-class)#exit

3-7

CCNP 2: Remote Access v 3.0 - Lab 9.8.1

Copyright 2003, Cisco Systems, Inc.

Enable Frame Relay traffic shaping on the S0/0 interface and configure the interface to use the
Frame Relay class TSLAB as follows:
SanJose1(config)#interface serial0/0
SanJose1(config-if)#frame-relay class TSLAB
SanJose1(config-if)#frame-relay traffic-shaping

Verify the CBWFQ configuration on the SanJose1 router as follows:

SanJose1#show policy-map int
Serial0/0: DLCI 102 Service-policy output: CBWFQ-CENTRAL
Class-map: HTTP-CLASS (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group 100
Queueing
Output Queue: Conversation 25
Bandwidth 50 (%) Max Threshold 64 (packets)
(pkts matched/bytes matched) 0/0
(depth/total drops/no-buffer drops) 0/0/0
Class-map: TELNET-CLASS (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group 101
Queueing
Output Queue: Conversation 26
Bandwidth 25 (%) Max Threshold 64 (packets)
(pkts matched/bytes matched) 0/0
(depth/total drops/no-buffer drops) 0/0/0
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any

Verify that CBWFQ is applied correctly to the Frame Relay interface as follows:
SanJose1#show frame-relay pvc 102
PVC Statistics for interface Serial0/0 (Frame Relay DTE)
DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0
input pkts 12
output pkts 10
in bytes 1108
out bytes 1040
dropped pkts 0
in pkts dropped 0
out pkts dropped 0
out bytes dropped 0
in FECN pkts 0
in BECN pkts 0
out FECN pkts 0
out BECN pkts 0
in DE pkts 0
out DE pkts 0
out bcast pkts 0
out bcast bytes 0
Shaping adapts to BECN
pvc create time 00:18:05, last time pvc status changed 00:15:47
cir 9600
bc 9600
be 0
byte limit 150
interval 125
mincir 4800
byte increment 150
Adaptive Shaping BECN
pkts 0
bytes 0
pkts delayed 0
bytes delayed 0
shaping inactive
traffic shaping drops 0
4-7

CCNP 2: Remote Access v 3.0 - Lab 9.8.1

Copyright 2003, Cisco Systems, Inc.

service policy CBWFQ-CENTRAL

Serial0/0: DLCI 102 Service-policy output: CBWFQ-CENTRAL
<Output Omitted >

Step 3
In this step, Low Latency Queuing will be implemented on the London router. On the London router,
create an extended ip access list 102 to simulate all low latency traffic such as voice over IP. To do
so, the access-list will permit traffic from the London sites loopback 0 interface to SanJose1 sites
LAN network.
London(config)#access-list 102 permit ip host 192.168.233.1
0.0.0.255

192.168.0.0

Create an extended ip access list 103 to permit traffic from the London sites loopback 1 interface to
SanJose1 sites LAN network.
London(config)#access-list 103 permit ip host 192.168.234.1
0.0.0.255

192.168.0.0

Create an extended ip access list 104 to permit traffic from the London sites loopback 2 interface to
SanJose1 sites LAN network.
London(config)#access-list 104 permit ip host 192.168.235.1
0.0.0.255

192.168.0.0

Three class maps need to be created to match the conditions of the access-lists. Create the first
class-map named LLQ-102-CLASS and configure a match condition with access list 102. Create the
second class-map named LLQ-103-CLASS and configure a match condition with access list 102.
Create the third class-map named LLQ-104-CLASS and configure a match condition with access list
102.
London(config)#class-map match-all LLQ-102-CLASS
London(config-cmap)#match access-group 102
London(config-cmap)#class-map match-all CBWFQ-103-CLASS
London(config-cmap)#match access-group 103
London(config-cmap)#class-map match-all CBWFQ-104-CLASS
London(config-cmap)#match access-group 104

Create a policy-map named CBWFQ-LONDON and configure a traffic policy for the class of traffic
named LLQ-102-CLASS specifying a priority of 8.
London(config-pmap)#policy-map CBWFQ-LONDON
London(config-pmap)#class LLQ-102-CLASS
London(config-pmap-c)#priority 8
London(config-pmap-c)#class CBWFQ-103-CLASS
London(config-pmap-c)#bandwidth percent 25
London(config-pmap-c)#class CBWFQ-104-CLASS
London(config-pmap-c)#bandwidth percent 25

Create a Frame Relay traffic shaping map-class called TSLAB. Set the CIR to 28000, the minimum
cir 18000, and the adaptive shaping to BECN. Finally, apply the service policy CBWFQ-LONDON as
follows:
London(config)#map-class frame-relay TSLAB
London(config-map-class)#frame-relay cir 28000
5-7

CCNP 2: Remote Access v 3.0 - Lab 9.8.1

Copyright 2003, Cisco Systems, Inc.

London(config-map-class)#frame-relay mincir 18000

London(config-map-class)#frame-relay adaptive-shaping becn
London(config-map-class)#service-policy output CBWFQ-LONDON

Step 4
Verifying the CBWFQ/LLQ configuration on the Branch router.
London#show policy-map
Policy Map CBWFQ-LONDON
Class LLQ-102-CLASS
Strict Priority
Bandwidth 8 (kbps) Burst 200 (Bytes)
Class CBWFQ-103-CLASS
Bandwidth 25 (%) Max Threshold 64 (packets)
Class CBWFQ-104-CLASS
Bandwidth 25 (%) Max Threshold 64 (packets)
Policy Map CBWFQ-BRANCH

Step 5
Generate traffic from the Singapore router to congest the London to the SanJose1 Frame Relay link.
Establish three connections to the Singapore router to generate significant network traffic. This must
be accomplished on all three extended ping sessions in a timely manner to congest the Frame Relay
link between the London and SanJose1 sites.
Note: It is very important that the following steps be read and understood before being attempted:
1. Establish a console session to the Singapore router.
2. Execute an extended ping to the SanJose1 router LAN interface using the loopback 0 address
as the source address. In addition, use 10,000 as the ping count with a byte size of 60 bytes.
This will simulate a voice over IP data flow.
3. While the extended ping is ongoing, exit the Singapore console connection and console to the
SanJose1 router.
4. Establish a Telnet session to the Singapore router from the SanJose1 router.
5. Execute an extended ping to the SanJose1 router LAN interface using the loopback 1 address
as the source address. In addition, use 10,000 as the ping count with a byte size of 1500 bytes.
This will simulate another IP data flow.
6. While the extended ping is ongoing, suspend the Telnet session by pressing Ctrl+Shift+6 twice
and then press X. This will go to the prompt on the SanJose1 router.
7. Establish a second Telnet session into the Singapore router from the SanJose1 router.
8. Execute an extended ping to the SanJose1 router LAN interface using the loopback 2 address
as the source address. In addition, use 10,000 as the ping count with a byte size of 1500 bytes.
This will simulate another IP data flow.
9. Exit the console session on the SanJose1 router.
10. Enter the London router through the console session.
11. On the London site router, use the show commands listed in the command list to complete the
following information:
Bandwidth allocated to the LLQ-102-CLASS: ______________
Bandwidth allocated to the CBWFQ-103-CLASS: ____________

6-7

CCNP 2: Remote Access v 3.0 - Lab 9.8.1

Copyright 2003, Cisco Systems, Inc.

Bandwidth allocated to the CBWFQ-104-CLASS: ____________

Drop rate for the CBWFQ-103-CLASS: ____________
Drop rate for the CBWFQ-104-CLASS: ____________
12. Erase the SanJose1, London, and Singapore router configurations and reload the routers.

7-7

CCNP 2: Remote Access v 3.0 - Lab 9.8.1

Copyright 2003, Cisco Systems, Inc.