Transcript
QOS
Implementing Cisco
Quality of Service
Version 2.2
Lab Guide
Editorial, Production, and Graphic Services: 06.28.06
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100
European Headquarters
Cisco Systems International BV
Haarlerbergpark
Haarlerbergweg 13-19
1101 CH Amsterdam
The Netherlands
www-europe.cisco.com
Tel: 31 0 20 357 1000
Fax: 31 0 20 357 1100
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
www.cisco.com
Tel: 408 526-7660
Fax: 408 527-0883
Asia Pacific Headquarters
Cisco Systems, Inc.
168 Robinson Road
#28-01 Capital Tower
Singapore 068912
www.cisco.com
Tel: +65 6317 7777
Fax: +65 6317 7799
Cisco Systems has more than 200 offices in the following countries and regions. Addresses, phone numbers, and fax numbers are listed on the
Cisco.comWebsiteatwww.cisco.com/go/offices.
Argentina • Australia • Austria • Belgium • Brazil • Bulgaria • Canada • Chile • China PRC • Colombia • Costa Rica • Croatia • Cyprus • Czech Republic •
Denmark • Dubai, UAE • Finland • France • Germany • Greece • Hong Kong SAR • Hungary • India • Indonesia • Ireland
Israel • Italy • Japan • Korea • Luxembourg • Malaysia • Mexico • The Netherlands • New Zealand • Norway • Peru • Philippines
Poland • Portugal • Puerto Rico • Romania • Russia • Saudi Arabia • Scotland • Singapore • Slovakia • Slovenia • South Africa
Spain • Sweden • Switzerland • Taiwan • Thailand • Turkey • Ukraine • United Kingdom • United States • Venezuela • Vietnam • Zimbabwe
© 2006 Cisco Systems, Inc. All rights reserved. CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of
Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access
Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press,
Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare,
GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace,
MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare,
SlideCast, SMARTnet, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates
in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a
partnership relationship between Cisco and any other company. (0601R)
DISCLAIMER WARRANTY: THIS CONTENT IS BEING PROVIDED “AS IS.” CISCO MAKES AND YOU RECEIVE NO WARRANTIES IN
CONNECTION WITH THE CONTENT PROVIDED HEREUNDER, EXPRESS, IMPLIED, STATUTORY OR IN ANY OTHER PROVISION OF
THIS CONTENT OR COMMUNICATION BETWEEN CISCO AND YOU. CISCO SPECIFICALLY DISCLAIMS ALL IMPLIED
WARRANTIES, INCLUDING WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR
PURPOSE, OR ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE. This learning product may contain early release
content, and while Cisco believes it to be accurate, it falls subject to the disclaimer above.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
QOS
Lab Guide
Overview
This guide presents the instructions and other information concerning the activities for this
course. You can find the solutions in the lab activity Answer Key.
Outline
This guide includes these activities:
Case Study 2-1: QoS Mechanisms
Lab 2-1: QoS Lab Setup and Initialization
Lab 2-2: Baseline QoS Measurement
Lab 3-1: Configuring QoS with AutoQoS
Case Study 4-1: Classification and Marking
Lab 4-1: Classification and Marking Using MQC
Lab 4-2: Classification Using NBAR
Lab 4-3: Configuring QoS Preclassify
Lab 4-4: LAN-Based Packet Classification and Marking
Lab 5-1: Configuring Basic Queuing
Lab 5-2: Configuring LLQ
Lab 5-3: Configuring Queuing on a Catalyst Switch
Case Study 6-1: WRED Traffic Profiles
Lab 6-1: Configuring DSCP-Based WRED
Lab 7-1: Configuring Class-Based Policing
Lab 7-2: Configuring Class-Based Shaping
Lab 8-1: Configuring Class-Based Header Compression
Lab 8-2: Configuring LFI
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Case Study 2-1: QoS Mechanisms
This case study enables you to practice the skills and knowledge learned in the modules
“Introduction to QoS” and “The Building Blocks of QoS.”
Activity Objective
In this activity, you will correctly identify which QoS mechanisms can be used, and where QoS
mechanisms should be applied to the network to implement an administrative QoS policy. After
completing this activity, you will be able to meet these objectives:
Review customer QoS requirements
Identify QoS service class requirements
Identify where QoS mechanisms should be applied to the network to meet customer
requirements
Present a solution to the case study
Visual Objective
The figure illustrates what you will accomplish in this activity.
Visual Objective for Case Study 2-1: QoS
Mechanisms
1. Review customer QoS requirements. Completely read the
customer requirements provided.
2. Identify QoS service class requirements. With the aid of your
partner, identify the service classes required to implement the
administrative QoS policy based on customer requirements.
3. Identify network locations where QoS classification and marking
should be applied. Identify locations in the network where the QoS
classification and marking mechanisms should be applied to
properly implement the administrative QoS policy.
4. Present your solution. After the instructor presents a solution to
the case study, present your solution to the class with your
partner.
© 2006 Cisco Systems, Inc. All rights reserved.
QoS v2.2—2
Required Resources
These are the resources and equipment required to complete this activity.
2
Case Study Activity: QoS Mechanisms
A workgroup consisting of two learners
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Apply QoS Mechanisms
This case study activity provides information regarding the QoS administrative policy
requirements of a large, multisite network. Your task is to work with a partner to evaluate the
QoS requirements, and based on the requirements, identify where QoS mechanisms should be
applied. You will discuss your solution with the instructor and other classmates, and the
instructor will present a solution for the case study to the class.
Task 1: Apply QoS Mechanisms
Step 1
Review customer QoS requirements.
Company Background
Nuevo Health Care Systems (NHCS) provides health care information to health care
professionals in ten major regions of the country.
Customer Situation
The NHCS network currently has limited bandwidth capacity in its WAN links, and the
company does not envision being able to increase bandwidth in the near future. All ten remote
sites (two are pictured in the network illustration) connect to the central site through a service
provider through a Frame Relay, Layer 2, 768-kbps link service. The NHCS headquarters site
also connects to the service provider via a Frame Relay, Layer 2, and 768-kbps link. NHCS
LAN bandwidth is 10 Mbps. NHCS connects to the Internet through its headquarters site.
Since the installation of a new IP telephony system, NHCS has been encountering the following
increasingly serious problems with their network:
Users of the ERP applications have been complaining of unacceptable response times.
Their subsecond response time has now stretched to multiple seconds in many cases and up
to a minute in some cases.
Key patient information files that used to arrive almost instantly are now taking 10 to 15
minutes to be transferred from headquarters to users at the remote sites. (These are
moderate sized, mostly text files.)
Patient graphics files (x-rays, MRIs) that used to take 20 to 30 minutes to transfer between
the remote sites and headquarters now often have to be transferred overnight. (This is
acceptable because these files are usually not needed immediately and tend to be extremely
large graphics files.)
Users of the new IP telephony devices are the most upset. The quality of their calls is very
poor, and their calls often just drop.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
3
Nuevo Health Systems Applications
© 2006 Cisco Systems, Inc. All rights reserved.
QoS v2.2—3
The key applications running on NHCS network are shown in the figure.
Nuevo Health Care Systems Network
n Device number on Problem Spreadsheet
© 2006 Cisco Systems, Inc. All rights reserved.
4
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
QoS v2.2—4
© 2006 Cisco Systems, Inc.
Device Number
Device Type
1
IP Phone
2
LAN switch
3
Customer edge router
4
Service provider router
Step 2
Identify QoS service class requirements.
Given the NHCS network as described, how would you recommend classifying network
traffic?
Traffic Classification and Prioritization
Type of Traffic (Application)
Step 3
Traffic Priority
(Rank from 1 to 5)
Identify network locations where QoS mechanisms should be applied.
Given the NHCS network as described, how would you recommend deploying QoS
mechanisms? Check each box (X) where you believe that QoS mechanisms could be applied to
effectively resolve QoS problems at NHCS.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
5
Where to Apply QoS Mechanisms: Classification and Marking
Device
No.
Network Device Interface
1
IP Phone—Interface to
workstation
1
IP Phone—Interface to switch
2
Switch—Interface to IP
Phone
2
Switch—Interface to
customer edge router
3
Customer edge router—
Interface to switch
3
Customer edge router—
Interface to WAN (service
provider router)
4
Service provider router—
Interface to customer edge
router
Classification
on Input
Classification
on Output
Marking
on Input
Marking
on
Output
Where to Apply QoS Mechanisms: Congestion Management and Avoidance
Device
No.
6
Network Device
Interface
2
Switch—Interface to IP
Phone
2
Switch—Interface to
customer edge router
3
Customer edge router—
Interface to switch
3
Customer edge router—
Interface to WAN
(service provider router)
4
Service provider router—
Interface to customer
edge router
Congestion
Management
on Input
Congestion
Management
on Output
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Congestion
Avoidance
on Input
Congestion
Avoidance
on Output
© 2006 Cisco Systems, Inc.
Where to Apply QoS Mechanisms: Traffic Policing and Traffic Shaping
Device
Network Device Interface
No.
2
Switch—Interface to IP Phone
2
Switch—Interface to customer edge
router
3
Customer edge router—Interface to
switch
3
Customer edge router—Interface to
WAN (service provider router)
4
Service provider router—Interface
to customer edge router
Traffic
Policing
on Input
Traffic
Policing
on Output
Traffic
Shaping
on Input
Traffic
Shaping
on Output
Where to Apply QoS Mechanisms: Link Efficiency
Device
Network Device Interface
No.
2
Switch—Interface to IP Phone
2
Switch—Interface to customer
edge router
3
Customer edge router—Interface
to switch
3
Customer edge router—Interface
to WAN (service provider router)
4
Service provider router—
Interface to customer edge router
Step 4
Compression
on Input
Compression
on Output
LFI on
Input
LFI on
Output
Present your solution.
Together with your partner, present your solution to the class. Include the following
information:
Customer service class requirements
Network diagrams indicating where classification and marking should be applied
Justification for differences from the solution presented by the instructor
Activity Verification
You have completed this activity when the instructor has verified your case study solution and
you have justified any major deviations from the solution supplied by the instructor.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
7
Case Study 2-1 Answer Key: QoS Mechanisms
Your case study discussion and solution should include:
Traffic classification and prioritization
Location of QoS mechanisms for
—
Classification and marking
—
Congestion management and avoidance
—
Link efficiency
Traffic Classification and Prioritization
Type of Traffic (Application)
Traffic Priority
IP Telephony
Highest—1
ERP
High—2
Patient information files
Moderate—3
Patient graphics files
Low—4
Browser traffic
Low—4
Where to Apply QoS Mechanisms: Classification and Marking
Device
Network Device Interface
Classification
on Input
1
IP Phone—Link to
workstation
X
1
IP Phone—Link to switch
X
2
Switch—Link to IP Phone
X
2
Switch—Link to customer
edge router
X
3
Customer edge router—Link
to switch
X
3
Customer edge router—Link
to WAN (service provider
router)
X
4
Service provider router—Link
to customer edge router
X
No.
Note
8
Classification
on Output
Marking
on Input
Marking
on
Output
X*
No,
trusted*
*The IP Phone will normally be set to re-mark any traffic coming from its downstream
workstation (the IP Phone connection to the workstation is “untrusted”). The switch will not
re-mark traffic coming from the IP Phone (traffic from the IP Phone is “trusted”). Further
explanation of “trusted” and “untrusted” interfaces is provided in the “Classification and
Marking” module of this course.
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Where to Apply QoS Mechanisms: Congestion Management and Avoidance
Device
No.
Network Device
Interface
Congestion
Management
on Input
Congestion
Management
on Output
Congestion
Avoidance
on Input
Congestion
Avoidance
on Output
2
Switch—Link to IP
Phone
X
2
Switch—Link to
customer edge router
X
3
Customer edge router—
Link to switch
X
3
Customer edge router—
Link to WAN (service
provider router)
X
Possible
4
Service provider
router—Link to
customer edge router
X
Possible
Possible
Where to Apply QoS Mechanisms: Traffic Policing and Traffic Shaping
Device
Network Device Interface
Traffic
Policing
on Input
2
Switch—Link to IP Phone
X
2
Switch—Link to customer edge
router
3
Customer edge router—Link to
switch
3
Customer edge router—Link to
WAN (service provider router)
4
Service provider router—Link to
customer edge router
No.
Traffic
Policing
on Output
Traffic
Shaping
on Input
Traffic
Shaping
on Output
X
Possible
X
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Possible
Lab Guide
9
Where to Apply QoS Mechanisms: Link Efficiency
Device
Network Device Interface
No.
Compression
on Output
2
Switch—Link to IP Phone
2
Switch—Link to customer edge
router
3
Customer edge router—Link to
switch
3
Customer edge router—Link to
WAN (service provider router)
X
4
Service provider router—Link to
customer edge router
X
Note
10
Compression
on Input
LFI on
Input
LFI on
Output
X
X
Because this is a Frame Relay network, the service provider will pass frames through
transparently without compressing or fragmenting the frames.
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Lab 2-1: QoS Lab Setup and Initialization
Complete this lab activity to practice what you learned in the modules “Introduction to QoS”
and “The Building Blocks of QoS.”
Activity Objective
In this activity, you will prepare your student workgroup for the lab practice exercises that
accompany the Implementing Cisco Quality of Service (QOS) v2.2 course. After completing
this activity, you will be able to meet these objectives:
Configure your workgroup routers for basic network connectivity
Configure your workgroup switch for basic network connectivity
Verify network connectivity using the Cisco IOS tools: ping and traceroute
Visual Objective
The figures illustrate what you will accomplish in this activity.
The lab topology for the course is split into a number of workgroups and three separate
backbones.
Each workgroup is designated to service two students and has been designed to interface with
two traffic generation backbones named “Traffic Gen 1” and “Traffic Gen 2” and a shared
provider backbone named “Provider.”
Visual Objective for Lab 2-1: QoS Lab Setup
and Initialization
© 2006 Cisco Systems, Inc. All rights reserved.
QoS v2.2—5
The figure shows the physical topology of a single workgroup and its connectivity into the
three lab backbones. Each workgroup consists of two user-controlled Cisco 2610XM routers
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
11
and one user-controlled Cisco 2950T-24 workgroup switch. Each student workgroup connects
to each backbone as shown in the figure.
Although depicted as two different workgroup switches in the “Logical Lab Backbone” figure,
each student workgroup consists of a single workgroup switch configured to support two
different virtual LANs. In this figure, the single workgroup switch has been depicted as two
different switches to simplify the diagram only. Notice that the same name has been used to
identify the Cisco 2950T, indicating that it is, in fact, the same device.
Traffic for each pod can bypass the high-speed service provider backbone (using the slow 384kbps link) or travel via the high-speed provider backbone itself (using the fast 768-kbps serial
link). Traffic flow through both the slow and fast serial links will be tested in the QoS labs.
In this figure, the logical topology configuration of each workgroup and the devices contained
within each of the three lab backbones is shown. In the Provider Backbone in the figure, each
of the backbone routers (SPNorth and SPSouth) contains a serial connection to each
workgroup.
The QoS lab uses the two routers called Pagent-1 and Pagent-2 to generate traffic from
different applications, including SQL, Napster, FTP, Citrix, HTTP, Microsoft Outlook, and
Kazaa. The two routers called Callgen-1 and Callgen-2 are used in the lab to generate (G.711)
VoIP traffic.
Note
12
The SPNorth router, the SPSouth router, the core switch, and the traffic generation routers
(Pagent-1, Pagent-2, Callgen-1, and Callgen-2) are preconfigured and managed by the
instructor.
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Logical Lab Backbone Topology
© 2006 Cisco Systems, Inc. All rights reserved.
QoS v2.2—6
Each Pagent and Callgen router is set up with connections to eight VLANs (one for each lab
workgroup) as follows:
Pagent-1 and Callgen-1 are configured with VLANs 11 to 18.
Pagent-2 and Callgen-2 are configured with VLANs 21 to 28.
Traffic flow to and from the Pagent and Callgen lab routers is designed to traverse the network
through each workgroup as follows:
Pagent-1 and Callgen-1 (VLAN 11) send traffic to Pagent-2 and Callgen-2 (VLAN 21) via
pod 1.
Pagent-1 and Callgen-1 (VLAN 12) send traffic to Pagent-2 and Callgen-2 (VLAN 22) via
pod 2.
Pagent-1 and Callgen-1 (VLAN 13) send traffic to Pagent-2 and Callgen-2 (VLAN 23) via
pod 3.
Pagent-1 and Callgen-1 (VLAN 14) send traffic to Pagent-2 and Callgen-2 (VLAN 24) via
pod 4.
Pagent-1 and Callgen-1 (VLAN 15) send traffic to Pagent-2 and Callgen-2 (VLAN 25) via
pod 5.
Pagent-1 and Callgen-1 (VLAN 16) send traffic to Pagent-2 and Callgen-2 (VLAN 26) via
pod 6.
Pagent-1 and Callgen-1 (VLAN 17) send traffic to Pagent-2 and Callgen-2 (VLAN 27) via
pod 7.
Pagent-1 and Callgen-1 (VLAN 18) send traffic to Pagent-2 and Callgen-2 (VLAN 28) via
pod 8.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
13
The logical configuration of each of these VLANs is as follows:
Lab VLAN Logical Address Assignments
Workgroup Pod
VLANs
Assigned IP Subnets
1
11 and 21
10.1.1.0/24 (VLAN 11) and 10.3.1.0/24 (VLAN 21)
2
12 and 22
10.1.2.0/24 (VLAN 12) and 10.3.2.0/24 (VLAN 22)
3
13 and 23
10.1.3.0/24 (VLAN 13) and 10.3.3.0/24 (VLAN 23)
4
14 and 24
10.1.4.0/24 (VLAN 14) and 10.3.4.0/24 (VLAN 24)
5
15 and 25
10.1.5.0/24 (VLAN 15) and 10.3.5.0/24 (VLAN 25)
6
16 and 26
10.1.6.0/24 (VLAN 16) and 10.3.6.0/24 (VLAN 26)
7
17 and 27
10.1.7.0/24 (VLAN 17) and 10.3.7.0/24 (VLAN 27)
8
18 and 28
10.1.8.0/24 (VLAN 18) and 10.3.8.0/24 (VLAN 28)
Required Resources
These are the resources and equipment required to complete this activity:
Lab topology configured for the QoS course
Student workgroup consisting of two user-controlled Cisco 2610XM routers and one usercontrolled Cisco 2950T-24 workgroup switch
Classroom reference materials as follows:
14
—
QoS Student Guide
—
QoS Lab Guide
Student pod workstation with Telnet or console access to workstation pod devices
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Command List
The table describes the commands used in this activity.
QoS Course Lab Setup and Initialization Lab Router Commands
Command
Description
hostname name
Specifies or modifies the host name
enable secret password
Configures the password for users to enter enable mode
interface interface-id
Enters interface configuration mode and the physical interface
identification
[no] ip address ip-address
mask
Sets a primary or secondary IP address for an interface
clock rate bps
Configures the clock rate for the hardware connections on serial
interfaces
bandwidth kbps
Sets and communicates to higher-level protocols the current
bandwidth value for an interface
encapsulation encapsulationtype
Sets the encapsulation method used by the interface
show ip interface [brief]
[type] [number]
Lists a summary of interface IP information and status
router ospf process-id
Configures an OSPF routing process
network ip-address wildcardmask area area-id
Defines the interfaces on which OSPF protocol runs and defines
the area ID for those interfaces
show ip ospf neighbor
Displays OSPF-neighbor information on a per-interface basis
shutdown
Disables an interface
copy running-config startupconfig
Saves your entries in the configuration file
QoS Course Lab Setup and Initialization Lab Switch Commands
Command
Description
hostname name
Specifies or modifies the host name
enable secret password
Configures password for users to enter enable mode
interface interface-id
Enters interface configuration mode and the physical interface
identification
show ip interface [brief]
[type] [number]
Lists a summary of interface IP information and status
show interfaces [interfaceid]
Displays the administrative and operational status of all interfaces
or a specified interface
copy running-config startupconfig
Saves your entries in the configuration file
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
15
Job Aid
This job aid is available to help you complete the lab activity:
Your assigned workgroup pod number provided by the instructor
Task 1: Configure Routers and Switch and Verify Connectivity
You will configure your workgroup routers for basic network connectivity.
Activity Procedure
Complete these steps:
Step 1
Step 2
Step 3
Note
16
Configure the host name and passwords on both of the workgroup routers in your
assigned workgroup pod as shown in this table (where x is your assigned workgroup
pod number).
Host Name
Enable Secret Password
VTY Login Password
WGxR1
cisco
cisco
WGxR2
cisco
cisco
Configure the IP address on the S0/0, S0/1, and Fa0/0 interfaces of the workgroup
routers in your assigned workgroup pod as shown in this table.
Interface
WGxR1
WGxR2
Fa0/0
10.1.x.1/24
10.3.x.2/24
S0/0
10.2.x.1/24
10.2.x.2/24
S0/1
10.4.x.1/24
10.5.x.2/24
Configure the clock rate on the S0/0 serial interface of your WGxR1 router to 384
kbps.
Interface
WGxR1 S0/0 clock rate
S0/0
384000 bps
In the service provider backbone, each of the backbone routers (SPNorth, SPSouth)
contains a serial connection to each workgroup router. The “Sy/x” table lists the IP
addressing requirements of these connections. Both service provider routers are the data
DCE with the clock rate configured by the instructor as 768 kbps.
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Sy/x
SPNorth IP Address
SPSouth IP Address
S0/0 – to pod 1
10.4.1.100
10.5.1.100
S0/1 – to pod 2
10.4.2.100
10.5.2.100
S0/2 – to pod 3
10.4.3.100
10.5.3.100
S0/3 – to pod 4
10.4.4.100
10.5.4.100
S1/0 – to pod 5
10.4.5.100
10.5.5.100
S1/1 – to pod 6
10.4.6.100
10.5.6.100
S1/2 – to pod 7
10.4.7.100
10.5.7.100
S1/3 – to pod 8
10.4.8.100
10.5.8.100
Step 4
Configure the S0/0 and S0/1 serial interfaces of your workgroup routers for PPP
encapsulation and set the bandwidth to match the clock rate configured in Step 3 of
this lab exercise.
Step 5
Administratively enable the S0/0, S0/1, and Fa0/0 interfaces on both of your
workgroup routers and verify that these interfaces are all in the “up” state
(administratively up, line protocol up).
If the Fa0/0 interface is down, log in to your workgroup switch to ensure that the
switch port is also administratively enabled.
WGxR1#show ip interface brief
Interface
FastEthernet0/0
Serial0/0
Serial0/1
Virtual-Access1
IP-Address
10.1.x.1
10.2.x.1
10.4.x.1
unassigned
OK?
YES
YES
YES
YES
Method
NVRAM
NVRAM
NVRAM
unset
Status
up
up
up
up
Protocol
up
up
up
up
Method
NVRAM
NVRAM
NVRAM
unset
Status
up
up
up
up
Protocol
up
up
up
up
WGxR2#show ip interface brief
Interface
FastEthernet0/0
Serial0/0
Serial0/1
Virtual-Access1
Step 6
IP-Address
10.3.x.2
10.2.x.2
10.5.x.2
unassigned
OK?
YES
YES
YES
YES
Configure an OSPF routing process on your workgroup routers and place the S0/0,
S0/1, and Fa0/0 interfaces into OSPF area 0.
router ospf 1
network 10.0.0.0 0.255.255.255 area 0
Step 7
Verify that both OSPF neighbors of your workgroup routers are in the “FULL” state.
Each of your workgroup routers should have a “FULL” neighbor relationship to the
service provider router and to the other workgroup router in your pod.
WGxR1#show ip ospf neighbor
Neighbor ID
10.10.10.100
10.5.x.2
Pri
0
0
State
FULL/FULL/-
Dead Time Address
00:00:37 10.4.x.100
00:00:36 10.2.x.2
Interface
Serialy/z
Serial0/0
WGxR2#show ip ospf neighbor
Neighbor ID
Pri
State
Dead Time Address
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Interface
Lab Guide
17
10.10.10.200
10.4.x.1
0
0
FULL/FULL/-
00:00:31
00:00:33
10.5.x.100
10.2.x.1
Serialy/z
Serial0/0
Step 8
Verify that the serial ports on both of your workgroup routers (WGxR1 and
WGxR2) have their queuing strategy set to WFQ.
Step 9
Configure the host name and password on the workgroup switch in your assigned
workgroup pod as shown in this table.
Host Name
Enable Secret Password
WGxS1
cisco
Activity Verification
You have completed this task when you attain this result:
You have configured your workgroup routers for basic network connectivity.
Task 2: Configure Workgroup Switch for Connectivity
You will configure your workgroup switch for basic network connectivity.
Activity Procedure
Complete these steps:
Step 1
From the global configuration mode, configure the VTP domain name and mode,
and VLANs 1x and 2x on your workgroup switch.
vtp domain qos
vtp mode transparent
!
vlan 1x
name vlan1x
vlan 2x
name vlan2x
!
end
Step 2
Configure 802.1Q trunking and access ports on the workgroup switch by
configuring the Fa0/1, Fa0/2, and Fa0/3 interfaces of your workgroup switch as
follows:
Fa0/1 is an 802.1Q trunk connected to the core switch. Only VLANs 1x and 2x
should be allowed on the trunk.
Fa0/2 should be an access port in VLAN 1x connected to the WGxR1 router.
Fa0/3 should be an access port in VLAN 2x connected to the WGxR2 router.
interface FastEthernet0/1
description - to core sw
switchport trunk allowed vlan 1x,2x
switchport mode trunk
no ip address
!
interface FastEthernet0/2
description - to WGxR1
switchport access vlan 1x
switchport mode access
no ip address
!
18
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
interface FastEthernet0/3
description - to WGxR2
switchport access vlan 2x
switchport mode access
no ip address
Step 3
Verify that the Fa0/1, Fa0/2, and Fa0/3 interfaces on the workgroup switch are all
up. Administratively enable any interfaces in the shutdown state.
WGxS1#sh ip int brief
Interface
Protocol
Vlan1
FastEthernet0/1
FastEthernet0/2
FastEthernet0/3
FastEthernet0/4
IP-Address
unassigned
unassigned
unassigned
unassigned
unassigned
OK?
YES
YES
YES
YES
YES
Method
manual
unset
unset
unset
unset
Status
administratively down down
up
up
up
up
up
up
down
down
[rest omitted]
Note
Step 4
In the lab, there is no requirement to ping to or from the workgroup switch. The workgroup
switch will not need an IP address configured on Interface VLAN 1 and will not need an IP
default gateway configuration.
From your WGxS1 switch, use the show interface fa0/x switchport command to
verify that the Fa0/1 interface 802.1Q trunking is on and only allow VLANs 1x and
2x on the trunk.
WGxS1#sh int fa 0/1 switchport
Name: Fa0/1
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Operational private-vlan: none
Trunking VLANs Enabled: 1x,2x
Pruning VLANs Enabled: 2-1001
Protected: false
Voice VLAN: none (Inactive)
Appliance trust: none
Step 5
Verify that the Fa0/2 interface is in VLAN 1x.
WGxS1#sh int fa 0/2 switchport
Name: Fa0/2
Switchport: Enabled
Administrative Mode: static access
Operational Mode: static access
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: native
Negotiation of Trunking: Off
Access Mode VLAN: 1x (VLAN001x)
Trunking Native Mode VLAN: 1 (default)
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Operational private-vlan: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
Protected: false
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
19
Voice VLAN: none (Inactive)
Appliance trust: none
Step 6
Verify that the Fa0/3 interface is in VLAN2x.
WGxS1#sh int fa 0/3 switchport
Name: Fa0/3
Switchport: Enabled
Administrative Mode: static access
Operational Mode: static access
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: native
Negotiation of Trunking: Off
Access Mode VLAN: 2x (VLAN002x)
Trunking Native Mode VLAN: 1 (default)
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Operational private-vlan: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
Protected: false
Voice VLAN: none (Inactive)
Appliance trust: none
Activity Verification
You have completed this task when you attain this result:
You have configured your workgroup switch for basic network connectivity.
Task 3: Verify Network Connectivity
You will verify network connectivity using the Cisco IOS tools: ping and traceroute.
Activity Procedure
Complete these steps:
Step 1
From the WGxR1 router, perform the following pings to confirm connectivity and
routing protocol operation:
Ping the SPNorth router (10.4.x.100).
WGxR1#ping 10.4.x.100
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.4.x.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms
Ping the SPSouth router Internet connection (10.10.10.200).
WGxR1#ping 10.10.10.200
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.10.200, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/8 ms
20
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Ping the WGxR2 router (10.2.x.2).
WGxR1#ping 10.2.x.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.2.x.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/16/16 ms
Ping the Pagent-1 (10.1.x.10) and Callgen-1 (10.1.x.11) routers.
WGxR1#ping 10.1.x.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.x.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/47/56 ms
WGxR1#ping 10.1.x.11
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.x.11, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Step 2
From the WGxR2 router, perform the following pings to confirm connectivity and
routing protocol operation:
Ping the SPSouth router (10.5.x.100).
WGxR2#ping 10.5.x.100
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.5.x.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms
Ping the SPNorth router Internet connection (10.10.10.100).
WGxR2#ping 10.10.10.100
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.10.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/5/8 ms
Ping the Pagent-2 (10.3.x.10) and Callgen-2 (10.3.x.11) routers.
Ping the Pagent-2 (10.3.x.10) and Callgen-2 (10.3.x.11) routers.
WGxR2#ping 10.3.x.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.3.x.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/47/56 ms
WGxR2#ping 10.3.x.11
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.3.x.11, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Step 3
On the WGxR1 and WGxR2 routers, administratively disable the serial 0/0
interface.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
21
Step 4
From the WGxR1 router, use Telnet to connect to the Pagent-1 router (10.1.x.10)
and perform a traceroute to the Pagent-2 router (10.3.x.10) to confirm that the path
from Pagent-1 to Pagent-2 flows through your pod (via the SPNorth and SPSouth
routers). Use the diagram in Figure 3 to verify your traceroute.
WGxR1#telnet 10.1.x.10
Trying 10.1.x.10 ... Open
User Access Verification
Username: super
Password: bowl
pagent-1>traceroute 10.3.x.10
Type escape sequence to abort.
Tracing the route to 10.3.x.10
1
2
3
4
5
10.1.x.1 68 msec 64 msec 60 msec
10.4.x.100 44 msec 56 msec 56 msec
10.10.10.200 48 msec 52 msec 48 msec
10.5.x.2 44 msec 52 msec 52 msec
10.3.x.10 32 msec * 44 msec
pagent-1>exit
[Connection to 10.1.1.10 closed by foreign host]
WGxR1#
Step 5
From the WGxR1 router, use Telnet to connect to the Callgen-1 (10.1.x.11) router
and perform a traceroute to the Callgen-2 router (10.3.x.11) to confirm that the path
from Callgen-1 to Callgen-2 flows through your pod (via the SPNorth and SPSouth
routers). Use the diagram in Figure 3 to verify your traceroute.
WGxR1>telnet 10.1.x.11
Trying 10.1.x.11 ... Open
User Access Verification
Username: super
Password: bowl
callgen-1>traceroute 10.3.x.11
Type escape sequence to abort.
Tracing the route to 10.3.x.11
1
2
3
4
5
10.1.x.1 68 msec 64 msec 60 msec
10.4.x.100 44 msec 56 msec 56 msec
10.10.10.200 48 msec 52 msec 48 msec
10.5.x.2 44 msec 52 msec 52 msec
10.3.x.11 32 msec * 44 msec
callgen-1>exit
[Connection to 10.1.x.10 closed by foreign host]
WGxR1#
Step 6
On the WGxR1 and WGxR2 routers, administratively enable the serial 0/0 interface.
Step 7
Use Telnet to connect to the Pagent-1 router (10.1.x.10) and perform a traceroute to
the Pagent-2 router (10.3.x.10) to confirm that the path from Pagent-1 to Pagent-2
now flows through your pod and via the slow 384-kbps serial connection between
your WGxR1 and WGxR2 routers. Use the diagram in Figure 3 to verify your
traceroute.
WGxR1#telnet 10.1.x.10
Trying 10.1.x.10 ... Open
User Access Verification
Username: super
22
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Password: bowl
pagent-1>traceroute 10.3.x.10
Type escape sequence to abort.
Tracing the route to 10.3.x.10
1 10.1.x.1 56 msec 52 msec 60 msec
2 10.2.x.2 116 msec 252 msec 48 msec
3 10.3.x.10 128 msec * 104 msec
pagent-1>exit
[Connection to 10.1.x.10 closed by foreign host]
WGxR1#
Step 8
Save your running configurations of the workgroup routers and the workgroup
switch to the startup configuration in NVRAM.
Step 9
Notify your instructor when you have completed this initial setup lab.
Activity Verification
You have completed this task when you attain these results:
Pings from the WGxR1 router to the SPNorth, WGxR2, Pagent-1, and Callgen-1 routers
are successful.
Pings from the WGxR2 router to the SPSouth, Pagent-2, and Callgen-2 routers are
successful.
A traceroute from the Pagent-1 router to the Pagent-2 router flows through your pod (via
the SPNorth and SPSouth routers) with the S0/0 interface in the shutdown state.
A traceroute from the Callgen-1 router to the Callgen-2 router flows through your pod (via
the SPNorth and SPSouth routers) with the S0/0 interface in the shutdown state.
A traceroute from the Pagent-1 router to the Pagent-2 router flows through your pod 384kbps serial link with all WGxR1 and WGxR2 serial interfaces administratively enabled.
Lab 2-1 Answer Key: QoS Lab Setup and Initialization
When you complete this activity, your router configuration will be similar to the following,
with differences that are specific to your device or workgroup.
WG1R1
hostname WG1R1
!
enable secret 5 $1$n4//$vbCjudYcBR3yNPJqI.1tT0
!
ip subnet-zero
!
interface FastEthernet0/0
ip address 10.1.1.1 255.255.255.0
duplex auto
speed auto
!
interface Serial0/0
bandwidth 384
ip address 10.2.1.1 255.255.255.0
encapsulation ppp
clockrate 384000
no fair-queue
!
interface Serial0/1
bandwidth 768
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
23
ip address 10.4.1.1 255.255.255.0
encapsulation ppp
!
router ospf 1
log-adjacency-changes
network 10.0.0.0 0.255.255.255 area 0
!
ip http server
ip classless
!
line con 0
line aux 0
line vty 0 4
password cisco
login
!
end
WG1R2
hostname WG1R2
!
enable secret 5 $1$07qt$nKIz/sUIIRYMZ7urfJPtp1
!
ip subnet-zero
!
interface FastEthernet0/0
ip address 10.3.1.2 255.255.255.0
duplex auto
speed auto
!
interface Serial0/0
bandwidth 384
ip address 10.2.1.2 255.255.255.0
encapsulation ppp
no fair-queue
!
interface Serial0/1
bandwidth 768
ip address 10.5.1.2 255.255.255.0
encapsulation ppp
!
router ospf 1
log-adjacency-changes
network 10.0.0.0 0.255.255.255 area 0
!
line con 0
line aux 0
line vty 0 4
password cisco
login
!
end
WG1S1
hostname WG1S1
!
enable secret 5 $1$Yq48$E3tAlJjcYAP9qJpdmr0nu.
!
vlan 11
name vlan11
!
vlan 21
name vlan21
ip subnet-zero
vtp domain qos
vtp mode transparent
!
interface FastEthernet0/1
switchport trunk allowed vlan 11,21
24
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
switchport mode trunk
no ip address
!
interface FastEthernet0/2
switchport access vlan 11
switchport mode access
no ip address
!
interface FastEthernet0/3
switchport access vlan 21
switchport mode access
no ip address
!
interface Vlan1
no ip address
no ip route-cache
shutdown
!
!
line con 0
line vty 5 15
!
end
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
25
Lab 2-2: Baseline QoS Measurement
Complete this lab activity to practice what you learned in the modules “Introduction to QoS”
and “The Building Blocks of QoS.”
Activity Objective
In this activity, you will create a baseline measurement of network traffic for use in evaluating
the effectiveness of applied QoS mechanisms. After completing this activity, you will be able
to meet these objectives:
Clear interface counters on Cisco routers and switches
Identify interface statistics, which are meaningful in traffic baselines
Use Cisco IOS monitoring commands and network connectivity tools (ping command) to
gather network response time data
Visual Objective
The figure illustrates what you will accomplish in this activity.
In this lab, when the connectivity is properly established for your pod, you will record traffic
statistics without any QoS configuration on your workgroup routers or workgroup switch. This
record of the workgroup traffic statistics will form a rough baseline QoS measurement for your
pod.
For this lab, no special tools, such as QPM, will be used to monitor QoS statistics. Instead,
Cisco IOS show commands and extended pings are used to form a rough baseline
measurement.
26
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Company Background
E-Commerce University is one of the most respected private universities in California based on
its progressive educational offerings, which include a Master of Science degree in ECommerce Administration and Implementations. E-Commerce University has a northern and
southern campus. The northern campus is located in Seattle, Washington, and the southern
campus is located in Santa Monica, California. Each of the campuses has a population of 500
students and a faculty staff of 50 professors and administrators.
Customer Situation
The E-Commerce University network currently has limited bandwidth capacity on its 384-kbps
leased line PPP WAN link that connects the northern and southern campuses, and the university
does not envision being able to increase bandwidth in the near future. Both campuses also have
a 768-kbps Internet connection. The preferred traffic path between the E-Commerce University
campuses is the 384-kbps link, because the 768-kbps link connects to the Internet and will have
a high path cost, even though it is a directly connected link with a higher bandwidth of 768
kbps.
The university has recently implemented these three new applications:
An IP telephony system between the northern and southern campus
An Oracle (SQL) student administration database system
Wireless Internet access for the students and faculties
Some of the other key applications currently running on the E-Commerce University network
that the university IT staff is aware of include the following:
Faculty remote access (Citrix)
MS Outlook e-mail (Microsoft Exchange)
Web server for accessing university information (HTTP)
Online courseware transfer between the northern and southern campuses (FTP)
Because of the deployment of these applications, the E-Commerce University has been
encountering these increasingly serious problems with their network:
Users of the Oracle (SQL) student administrations database system have been complaining
of unacceptable response times. Their subsecond response time has now stretched to
multiple seconds in many cases and up to a minute in some cases.
Users of the new IP telephony devices are the most upset. The quality of their calls is very
poor, and their calls often just drop.
Customer Requirements
At this point, E-Commerce University is most concerned about the low VoIP voice quality and
has called upon you (the new network engineer they hired in the last month) to perform a
baseline measurement of the VoIP traffic via the low-speed 384-kbps leased line connection
between the northern and southern campuses.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
27
Required Resources
These are the resources and equipment required to complete this activity:
Lab topology configured for QoS course
Student workgroup consisting of two user-controlled Cisco 2610XM routers and one usercontrolled Cisco 2950T-24 workgroup switch
Classroom reference materials as follows:
—
QoS Student Guide
—
QoS Lab Guide
Student pod workstation with Telnet or console access to workstation pod devices
Command List
The table describes the commands used in this activity.
Baseline QoS Measurement Lab Commands
Command
Description
show ip interface [brief]
[type] [number]
Lists a summary of an interface IP information and status
clear counters
Clears the interface counters
show interfaces [interfaceid]
Displays the administrative and operational status of all interfaces
or a specified interface
shutdown
Disables an interface
copy running-config startupconfig
Saves your entries in the configuration file
Job Aid
This job aid is available to help you complete the lab activity:
Your assigned workgroup pod number provided by the instructor
Task 1: Baseline Measurement of Network Traffic
You will clear interface counters on Cisco routers and switches.
Activity Procedure
Complete these steps:
28
Step 1
Verify that the S0/0 and S0/1 interfaces on both of your workgroup routers (WGxR1
and WGxR2) are administratively enabled.
Step 2
Clear the interface counters on both of your workgroup routers using the clear
counters command.
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Note
At this time, your instructor has not yet started the Pagent and Callgen router traffic
generations.
Activity Verification
You have completed this task when you attain this result:
You have cleared interface counters on Cisco routers and switches.
Task 2: Identify Interface Statistics
You will identify interface statistics.
Activity Procedure
Complete these steps:
Step 1
From the WGxR1 workgroup router, perform an extended ping to the WGxR2 router
serial 0/0 interface, then record the ping response time in the table at the end of the
lab. For the extended ping, use a repeat count of 100 and a datagram size of 160.
WGxR1#ping
Protocol [ip]:
Target IP address: 10.2.x.2
Repeat count [5]: 100
Datagram size [100]: 160
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 100, 160-byte ICMP Echos to 10.2.x.2, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (100/100), round-trip min/avg/max = 8/8/13 ms
Step 2
Repeat the extended ping two more times and record your results in the table at the
end of this lab.
Step 3
Repeat Step 1 and Step 2, but ping from the WGxR2 to WGxR1 serial 0/0 interface
and record the response time results in the table at the end of this lab.
Step 4
From both of your workgroup routers, issue the show interfaces serial 0/0
command and record the highlighted stats below in the table at the end of the lab.
WGxR1#show interfaces serial0/0
Serial0/0 is up, line protocol is up
Hardware is PowerQUICC Serial
Description: to WGxR2
Internet address is 10.2.3.1/24
MTU 1500 bytes, BW 384 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, LCP Open
Open: CDPCP, IPCP, loopback not set
Last input 00:00:03, output 00:00:01, output hang never
Last clearing of "show interface" counters 00:00:12
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queuing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/21/32 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 288 kilobits/sec
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
3 packets input, 429 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
29
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
3 packets output, 184 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
Step 5
Clear the interface counters on both of your workgroup routers using the clear
counters command.
Step 6
Notify your instructor when you are done with the prior steps. Your instructor will
start both Pagent and Callgen traffic generators. Your instructor will advise you
when all traffic streams are operational.
Activity Verification
You have completed this task when you attain this result:
You have identified interface statistics.
Task 3: Use Commands and Tools to Gather Network Response
Time Data After Both Pagent and Callgen Traffic Generators
Are Sending Traffic
You will use Cisco IOS monitoring commands and network connectivity tools (ping) to gather
network response time data.
Activity Procedure
Complete these steps:
Step 1
Caution
From the WGxR1 workgroup router, perform an extended ping to the WGxR2 router
serial 0/0 interface, then record the ping response time in the table at the end of the
lab. For the extended ping, use a repeat count of 100 and a datagram size of 160.
Before initiating the extended ping command, wait for the Pagent and Callgen traffic to run
for at least one minute so that the traffic generation can stabilize.
WGxR1#ping
Protocol [ip]:
Target IP address: 10.2.x.2
Repeat count [5]: 100
Datagram size [100]: 160
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 100, 160-byte ICMP Echos to 10.2.x.2, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (100/100), round-trip min/avg/max = 12/62/220 ms
Caution
30
After the Pagent traffic generation has been started, it is important that the Pagent routers
not be used for network measurements using ping and traceroute commands, because the
Pagent routers maintain a very high CPU load in generating the traffic demands for the QoS
course labs.
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Step 2
Repeat the extended ping command two more times and record your results in the
table at the end of this lab.
Step 3
Repeat Step 1 and Step 2 but ping from the WGxR2 to WGxR1 serial 0/0 interface
and record the response time results in the table at the end of this lab.
Step 4
From both of your workgroup routers, issue the show interfaces serial 0/0
command and record the highlighted statistics below in the table at the end of the
lab.
WGxR1#show interfaces serial 0/0
Hardware is PowerQUICC Serial
Description: to wgxr1
Internet address is 10.2.x.1/24
MTU 1500 bytes, BW 384 Kbit, DLY 20000 usec,
reliability 255/255, txload 130/255, rxload 37/255
Encapsulation PPP, LCP Open
Open: CDPCP, IPCP, loopback not set
Last input 00:00:02, output 00:00:00, output hang never
Last clearing of "show interface" counters 00:01:20
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 1023
Queueing strategy: weighted fair
Output queue: 0/1000/64/1023 (size/max total/threshold/drops)
Conversations 0/32/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 288 kilobits/sec
5 minute input rate 57000 bits/sec, 116 packets/sec
5 minute output rate 196000 bits/sec, 211 packets/sec
6595 packets input, 800344 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
9418 packets output, 826272 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
Note
The traffic sent between Pagent-1 and Pagent-2 is set up so that the traffic rate varies
constantly and will be different between Pagent-1 and Pagent-2. When the traffic rate from
Pagent-1 to Pagent-2 is high and increasing, the traffic rate from Pagent-2 to Pagent-1 will
be low and decreasing, and vice versa. As a result, the drop rate on your workgroup router
serial 0/0 interface may be different between your workgroup R1 and R2 routers.
Note
For Callgen, both Callgen routers will generate VoIP calls at a constant rate.
Step 5
Compare the resulting statistics with and without the Pagent and Callgen traffic
generations enabled.
You should notice that many of the pings would have a longer response time in the
event of congestion on the low bandwidth 384-kbps PPP serial link.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
31
Baseline QoS Measurement Lab Results
These four tables are used to record the results of your lab testing in this exercise. Record your
extended ping results in these two tables:
WGxR1 to WGxR2 QoS Baseline Ping Results
Packet Size
160 bytes
Without Pagent and
Callgen
With Pagent and
Callgen
min/avg/max
min/avg/max
success rate %
success rate %
Extended ping 1
Extended ping 2
Extended ping 3
Extended ping 1
Extended ping 2
Extended ping 3
WGxR2 to WGxR1 QoS Baseline Ping Results
Packet Size
160 bytes
Without Pagent and
Callgen
With Pagent and
Callgen
min/avg/max
min/avg/max
success rate %
success rate %
Extended ping 1
Extended ping 2
Extended ping 3
Extended ping 1
Extended ping 2
Extended ping 3
32
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Record your WGxR1 show interfaces serial 0/0 command results in this table.
WGxR1 QoS Baseline show interfaces Command Results
Without Pagent and
Callgen
With Pagent and Callgen
Queuing Strategy
Reliability, Txload, Rxload
Total Output Drops
Output Queue: size/max total
Output Queue: threshold/drops
Packets Output
Drop % (Calculated by you as:
Total Output Drop / Packets
Output)
Record your WGxR2 show interfaces serial 0/0 command results in this table.
WGxR2 QoS Baseline show interfaces Command Results
Without Pagent and
Callgen
With Pagent and Callgen
Queuing Strategy
Reliability, Txload, Rxload
Total Output Drops
Output Queue: size/max total
Output Queue: threshold/drops
Packets Output
Drop % (Calculated by you as:
Total Output Drop / Packets
Output)
Activity Verification
You have completed this task when you attain this result:
You have successfully completed the QoS baseline measurement by recording ping and
interface statistics both before and after network traffic generation.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
33
Lab 2-2 Answer Key: Baseline QoS Measurement
When you complete this activity, your router configuration will be similar to the following,
with differences that are specific to your device or workgroup.
Sample WGxR1 to WGxR2 QoS Baseline ping Results
Packet Size
Without Pagent and
Callgen
With Pagent and
Callgen
160 bytes
min/avg/max
min/avg/max
Extended ping 1
8/8/12
8/43/120
Extended ping 2
8/8/12
16/42/116
Extended ping 3
8/9/16
12/43/112
success rate %
success rate %
Extended ping 1
100%
100%
Extended ping 2
100%
100%
Extended ping 3
100%
100%
Sample WGxR1 QoS Baseline show interfaces Results
34
Without Pagent and
Callgen
With Pagent and Callgen
Queuing Strategy
WFQ (fair queue)
WFQ (fair queue)
Reliability, Txload, Rxload
255, 1, 1
255, 209, 39
Total Output Drops
0
1975
Output Queue: size/max total
0/1000
61/1000
Output Queue: threshold/drops
64/0
64/1975
Packets Output
3001
131760
Drop % (Calculated by you as:
Total Output Drop / Packets
Output)
0/3001 = 0
1975/131760 = 1.5%
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Lab 3-1: Configuring QoS with AutoQoS
Complete this lab activity to practice what you learned in the module “Introduction to Modular
QoS CLI and AutoQoS.”
Activity Objective
In this activity, you will configure QoS for VoIP on Cisco IOS routers and Catalyst switches
using AutoQoS. After completing this activity, you will be able to meet these objectives:
Configure AutoQoS on Cisco IOS routers
Configure AutoQoS on the Catalyst 2950 workgroup switch
Use Cisco IOS monitoring commands and network connectivity tools (ping) to gather
network response time data
Visual Objective
The figure illustrates what you will accomplish in this activity.
From the baseline measurement results, the E-Commerce University IT staff has determined
that the drop rate and the latency of the VoIP traffic must be improved. At this point, the ECommerce University has called upon you (the new CCNA network engineer they hired last
month) to improve the voice quality as quickly as possible over the weekend.
By the way, the E-Commerce University network is built using Cisco Catalyst 2950 switches,
Cisco 2610XM routers, and Cisco Aironet Wireless Access Points.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
35
Through Cisco online e-learning, you discovered the new AutoQoS for VoIP feature that
allows automated configuration of quality of service (QoS) on the network and provides a
means for simplifying the implementation and provisioning of QoS for VoIP traffic.
Because you have only a limited amount of time to implement a solution, you have decided to
go ahead and use AutoQoS and then test and compare the VoIP QoS results to see if AutoQoS
can be used to solve the problem.
Required Resources
These are the resources and equipment required to complete this activity:
Lab topology configured for QoS
Student workgroup consisting of two user-controlled Cisco 2610XM routers and one usercontrolled Cisco 2950T-24 workgroup switch
Classroom reference materials as follows:
—
QoS Student Guide
—
QoS Lab Guide
Student pod workstation with Telnet or console access to workstation pod devices
Command List
The table describes the commands used in this activity.
Configuring QoS with AutoQoS Lab Router Commands
36
Command
Description
show running-config
Displays the contents of the currently running configuration file
ip cef
Enables CEF on the router
interface interface-id
Enters interface configuration mode and the physical interface
identification
auto qos voip
Configures the AutoQoS-VoIP feature on an interface
show auto qos [interface
[interface-type]]
Displays the configuration created by the AutoQoS-VoIP feature
on a specific interface or all interfaces
show ip interface [brief]
[type] [number]
Lists a summary of an interface IP information and status
show interfaces multilink
[interface-id]
Displays the administrative and operational status of all interfaces
or a specified interface
clear counters
Clears the interface counters
encapsulation encapsulationtype
Sets the encapsulation method used by the interface
copy running-config startupconfig
Saves your entries in the configuration file
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Configuring QoS with AutoQoS Lab Switch Commands
Command
Description
interface interface-id
Enters interface configuration mode and the physical interface
identification
auto qos voip
Configures AutoQoS for VoIP within a QoS domain
show auto qos [interface
[interface-id]]
Displays AutoQoS configuration that is applied
copy running-config startupconfig
Saves your entries in the configuration file
Job Aid
This job aid is available to help you complete the lab activity:
Your assigned workgroup pod number provided by the instructor
Task 1: Configuring AutoQoS on Cisco IOS Routers
In this task, you will enable the AutoQoS for VoIP feature on your workgroup router low
bandwidth PPP serial interface.
Activity Procedure
Complete these steps:
Step 1
Display and examine the running configuration of your WGxR1 router.
Step 2
Enable CEF on your WGxR1 router.
Step 3
Enable the AutoQoS for VoIP feature for traffic on the S0/0 interface of WGxR1
only. Do not configure AutoQoS to trust DSCP markings.
Step 4
Display and examine the resulting AutoQoS configuration after enabling AutoQoS.
The following example outputs are from WG1.
ip access-list extended AutoQoS-VoIP-RTCP
permit udp any any range 16384 32767
!
ip access-list extended AutoQoS-VoIP-Control
permit tcp any any eq 1720 (3 matches)
permit tcp any any range 11000 11999
permit udp any any eq 2427
permit tcp any any eq 2428
permit tcp any any range 2000 2002
permit udp any any eq 1719
permit udp any any eq 5060
!
class-map match-any AutoQoS-VoIP-RTP-UnTrust
match protocol rtp audio
match access-group name AutoQoS-VoIP-RTCP
!
class-map match-any AutoQoS-VoIP-Control-UnTrust
match access-group name AutoQoS-VoIP-Control
!
class-map
match ip
match ip
match ip
match-any AutoQoS-VoIP-Re-mark
dscp ef
dscp cs3
dscp af31
!
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
37
policy-map AutoQoS-Policy-UnTrust
class AutoQoS-VoIP-RTP-UnTrust
priority percent 70
set dscp ef
class AutoQoS-VoIP-Control-UnTrust
bandwidth percent 5
set dscp af31
class AutoQoS-VoIP-Re-mark
set dscp default
class class-default
fair-queue
Serial0/0 !
interface Serial0/0
no ip address
encapsulation ppp
no fair-queue
ppp multilink
multilink-group 2001100114
!
interface Multilink2001100114
bandwidth 384
ip address 10.2.1.1 255.255.255.0
service-policy output AutoQoS-Policy-UnTrust
ppp multilink
ppp multilink fragment-delay 10
ppp multilink interleave
ip rtp header-compression iphc-format
!
rmon event 33333 log trap AutoQoS description "AutoQoS SNMP traps for Voice
Drops" owner AutoQoS
rmon alarm 33334 cbQosCMDropBitRate.1145.1147 30 absolute rising-threshold
1 33333 falling-threshold 0 owner AutoQoS
Step 5
Repeat Steps 1 through 4 for WGxR2.
Step 6
Issue the show ip interface brief command on WGxR1 and ensure that the Multilink
interface is up. The Multilink interface is required for PPP multilink and interleaving
operation. Notice that the S0/0 IP address assignment is automatically moved to the
Multilink interface.
WGxR1#show ip interface brief
Note
Step 7
Interface
IP-Address
OK? Method Status
Protocol
FastEthernet0/0
10.1.1.1
YES NVRAM
up
up
Serial0/0
unassigned
YES unset
up
up
Serial0/1
10.4.1.1
YES NVRAM
administratively down down
Virtual-Access1
unassigned
YES unset
up
up
Multilink2001100114
10.2.1.1
YES unset
up
up
Because Callgen is used to generate the VoIP traffic, the voice quality of the VoIP phone
calls cannot be tested directly. Therefore, after AutoQoS has been enabled, you will modify
the resulting QoS configurations to make the ping traffic (icmp echo and reply) to have the
same EF PHB as the VoIP traffic. In this way, you can compare the extended ping
responses with AutoQoS enabled to the responses before AutoQoS was enabled.
On the WGxR1 router, modify the ip access-list extended AutoQoS-VoIP-RTCP to
include the ping traffic (icmp echo and echo reply).
ip access-list extended AutoQoS-VoIP-RTCP
permit udp any any range 16384 32767
permit icmp any any echo
38
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
permit icmp any any echo-reply
Step 8
Repeat Step 7 for the WGxR2 router.
Activity Verification
You have completed this task when you attain these results:
You have successfully enabled the AutoQoS for VoIP feature on both WGxR1 and
WGxR2.
You have configured ping (ICMP echo and reply) to belong to the same traffic class as
VoIP traffic.
Task 2: Configuring AutoQoS on the Catalyst 2950 Switch
In this task, you will enable the AutoQoS for VoIP feature on your workgroup Catalyst 2950
switch.
Activity Procedure
Complete these steps:
Step 1
Display and examine the running configuration of your WGxS1 switch.
Step 2
Enable the AutoQoS for VoIP feature for traffic on the Fa0/1 interface of WGxS1 and
trust the CoS markings from the core switch.
Step 3
Display and examine the resulting AutoQoS configuration after enabling AutoQoS.
Notice that the 2950 is now configured for WRR queuing with queue 4 setup as the
expedite queue (weight = 0). WRR queuing will be covered in the module
“Congestion Management.”
Initial configuration applied by AutoQoS:
wrr-queue bandwidth 20 1 80 0
no wrr-queue cos-map
wrr-queue cos-map 1 0 1 2 4
wrr-queue cos-map 3 3 6 7
wrr-queue cos-map 4 5
mls qos map cos-dscp 0 8 16 26 32 46 48 56
!
interface FastEthernet0/1
mls qos trust cos
auto qos voip trust
Activity Verification
You have completed this task when you attain this result:
You have successfully enabled the AutoQoS for VoIP feature on WGxS1.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
39
Task 3: QoS Baseline with AutoQoS
In this task, you will use Cisco IOS monitoring commands and network connectivity tools
(ping) to gather network response time data. You will compare the results of the traffic
statistics of the network baseline statistics captured in Lab Exercise 2-2 and the network
statistics after the application of AutoQoS.
Activity Procedure
Complete these steps:
Step 1
Refer to Lab 2-2 and copy the baseline traffic information with the Pagent and
Callgen traffic generation running into the tables at the end of this lab.
Step 2
From the WGxR1 workgroup router, perform an extended ping to the WGxR2 router
serial 0/0 interface, then record the ping response time in the table at the end of the
lab. For the extended ping, use a repeat count of 100 and a datagram size of 160.
WGxR1#ping
Protocol [ip]:
Target IP address: 10.2.x.2
Repeat count [5]: 100
Datagram size [100]: 160
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 100, 160-byte ICMP Echos to 10.2.x.2, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (100/100), round-trip min/avg/max = 28/49/89 ms
Step 3
Repeat the extended ping two more times and record your results in the table at the
end of this lab.
Step 4
Repeat Steps 2 and 3, but ping from the WGxR2 to WGxR1 serial 0/0 interface and
record the response time results in the table at the end of this lab.
Step 5
Clear the interface counters on both of your workgroup routers using the clear
counters command.
Step 6
Wait for the interface counters to accumulate traffic statistics for at least one minute.
Step 7
From both of your workgroup routers, issue the show interfaces multilink command
and record the highlighted statistics below in the table at the end of the lab.
WGxR1#show interfaces Multilink2001100114
MMultilink2001100114 is up, line protocol is up
Hardware is multilink group interface
Internet address is 10.2.x.2/24
MTU 1500 bytes, BW 384 Kbit, DLY 100000 usec,
reliability 255/255, txload 23/255, rxload 5/255
Encapsulation PPP, LCP Open, multilink Open
Open: IPCP, loopback not set
DTR is pulsed for 2 seconds on reset
40
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Last input 00:00:09, output never, output hang never
Last clearing of "show interface" counters 00:01:15
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 1415
Queueing strategy: weighted fair
Output queue: 151/1000/64/1415/3541 (size/max
total/threshold/drops/interleaves)
Conversations 21/30/128 (active/max active/max total)
Reserved Conversations 1/1 (allocated/max allocated)
Available Bandwidth 1 kilobits/sec
5 minute input rate 9000 bits/sec, 19 packets/sec
5 minute output rate 35000 bits/sec, 37 packets/sec
4926 packets input, 217664 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
11486 packets output, 1358207 bytes, 0 underruns
0 output errors, 0 collisions, 4 interface resets
0 output buffer failures, 0 output buffers swapped out
Step 8
Compare the results of the traffic statistics from Lab 2-2 QoS Baseline Measurement
to the results from this lab.
Is the ping maximum response time shorter than before AutoQoS was enabled?
Explain. ___________________________________________________________
Is the drop rate higher, lower, or about the same as before AutoQoS was enabled?
Explain. ____________________________________________________
Step 9
Remove the AutoQoS configuration on your workgroup switch and workgroup
routers.
WGxS1(config)#int fa0/1
WGxS1(config-if)#no auto qos voip
WGxS1(config-if)#end
WGxS1#show auto qos
AutoQoS is disabled
Note
If a newer IOS version on the Catalyst 2950 is used, the no auto qos voip command will
not remove the global QoS configurations that were enabled by AutoQoS. You need to
remove them manually. (Refer to Task 2, Step 3 for the global QoS configurations.)
WGxR1(config)#int s0/0
WGxR1(config-if)#no auto qos voip
WGxR2(config)#int s0/0
WGxR2(config-if)#no auto qos voip
Note
When removing AutoQoS from WGxR1 and WGxR2, the encapsulation on your serial
interfaces may be returned to HDLC, the Cisco default serial interface encapsulation. Be
sure to reconfigure your serial interfaces for PPP encapsulation on both WGxR1 and
WGxR2.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
41
Step 10
On both of your workgroup routers, issue the show ip interface brief command and
ensure that the serial 0/0 interface is up. The Multilink interface should be removed
when AutoQoS has been disabled.
WGxR1#sh ip int brief
Interface
IP-Address OK? Method
Protocol
YES NVRAM up
Serial0/0
10.2.x.1
YES unset
Serial0/1
10.4.1.1
YES NVRAM administratively down down
Virtual-Access1 unassigned YES unset
Step 11
Status
FastEthernet0/0 10.1.1.1
up
up
up
up
up
Save your running configurations of the workgroup routers and the workgroup switch
to the startup-config in NVRAM.
Configuring QoS with AutoQoS Lab Results
Record your extended ping results in the two tables below:
WGxR1 to WGxR2 AutoQoS ping Results
Packet Size
160 bytes
Without AutoQoS
(From Lab 2-2)
With AutoQoS
(This Lab)
min/avg/max
min/avg/max
success rate %
success rate %
Extended ping 1
Extended ping 2
Extended ping 3
Extended ping 1
Extended ping 2
Extended ping 3
42
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
WGxR2 to WGxR1 AutoQoS ping Results
Packet Size
160 bytes
Without AutoQoS
(From Lab 2-2)
With AutoQoS
(This Lab)
min/avg/max
min/avg/max
success rate %
success rate %
Extended ping 1
Extended ping 2
Extended ping 3
Extended ping 1
Extended ping 2
Extended ping 3
Record your WGxR1 show interfaces multilink results in this table:
WGxR1 AutoQoS show interfaces Results
Without AutoQoS
(From Lab 2-2)
show interface s0/0
With AutoQoS
(This Lab)
show interface multilink
Queuing Strategy
Reliability, Txload, Rxload
Total Output Drops
Output Queue: size/max total
Output Queue:
threshold/drop/interleaves
Packets Output
Drop % (Calculated by you as:
Total Output Drop / Packets
Output)
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
43
Record your WGxR2 show interfaces serial 0/0 results in this table:
WGxR2 AutoQoS show interfaces Results
Without AutoQoS
(From Lab 2-2)
show interface s0/0
With AutoQoS
(This Lab)
show interface multilink
Queuing Strategy
Reliability, Txload, Rxload
Total Output Drops
Output Queue: size/max total
Output Queue:
threshold/drop/interleaves
Packets Output
Drop % (Calculated by you as:
Total Output Drop / Packets
Output)
Activity Verification
You have completed this task when you attain these results:
You have successfully completed the QoS baseline measurement after enabling AutoQoS
by recording ping and interface statistics.
You have compared the results of the traffic measurement to those from the QoS Baseline
Lab and correctly answered the questions contained within the lab.
You have successfully removed AutoQoS configuration from your workgroup routers and
switch.
Lab 3-1 Answer Key: Configuring QoS with AutoQoS
When you complete this activity, your router configuration will be similar to the following,
with differences that are specific to your device or workgroup.
Step 1
The following configuration is entered to enable AutoQoS on the WGxR1 and
WGxR2 routers:
interface serial 0/0
auto qos voip
ip access-list extended AutoQoS-VoIP-RTCP
permit udp any any range 16384 32767
permit icmp any any echo
permit icmp any any echo-reply
Step 2
The following configuration is entered to enable AutoQoS on the WGxS1 switch:
interface fastethernet 0/1
auto qos voip trust
Step 3
44
The following are the answers to the questions in this lab exercise:
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Is the ping maximum response time shorter than before AutoQoS was enabled? Explain.
Yes, because ping was moved into the expedited forwarding class with VoIP traffic. The
minimum time may be higher because the traffic generation tools are generating traffic at
different data rates.
Is the drop rate higher, lower, or about the same as before AutoQoS was enabled? Explain.
The drop rate is about the same because AutoQoS only affects the voice over IP traffic
and not the data traffic. The VoIP traffic load in the lab is minimal compared to the data.
The following are sample QoS Lab results:
Sample WGxR1 to WGxR2 AutoQoS ping Results
Packet Size
Without AutoQoS
(From Lab 2-2)
With AutoQoS
(This Lab)
160 bytes
min/avg/max
min/avg/max
Extended ping 1
8/43/120
32/54/88
Extended ping 2
16/42/116
32/53/88
Extended ping 3
12/43/112
32/54/88
success rate %
success rate %
Extended ping 1
100%
100%
Extended ping 2
100%
100%
Extended ping 3
100%
100%
Sample WGxR1 AutoQoS show interfaces Results
Without AutoQoS
(From Lab 2-2)
show interface s0/0
With AutoQoS
(This Lab)
show interface multilink
Queuing Strategy
WFQ (fair queue)
WFQ (fair queue)
Reliability, Txload, Rxload
255, 209, 39
255, 245, 41
Total Output Drops
1975
216
Output Queue: size/max total
61/1000
161/1000
Output Queue:
threshold/drop/interleaves
64/1975
64/216/8534
Packets Output
131760
20530
Drop % (Calculated by you as:
Total Output Drop / Packets
Output)
1975/131760 = 1.5%
216/20530=1.1%
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
45
Case Study 4-1: Classification and Marking
This case study enables you to practice the skills and knowledge learned in the module
“Classification and Marking.”
Activity Objectives
In this activity, you will define a QoS policy that assigns network traffic to service classes and
identify where classification and marking should be applied to the network. Upon completing
this activity, you will be able to meet these objectives:
Review customer QoS requirements
Identify QoS service class requirements
Identify network locations where classification and marking should be applied
Present a solution to the case study
Visual Objective
The figure illustrates what you will accomplish in this activity.
Visual Objective for Case Study 6-1:
WRED Traffic Profiles
1. Review customer QoS requirements. Completely read the
customer requirements provided.
2. Identify QoS service class requirements. With the aid of your
partner, identify the service classes required to implement the
administrative QoS policy based on customer requirements.
3. Create WRED traffic profiles. Create the WRED traffic profiles
required to properly implement the administrative QoS policy.
4. Present Your Solution. After the instructor presents a solution to
the case study, present your solution to the class with your
partner.
© 2006 Cisco Systems, Inc. All rights reserved.
QoS v2.2—29
Required Resources
These are the resources and equipment required to complete this activity:
46
Case Study Activity: Classification and Marking with QoS Service Classes
A workgroup consisting of two learners
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Case Study Classification and Marking
This case study provides information regarding the QoS administrative policy requirements of a
large, multisite network. Your task is to work with a partner to evaluate the QoS requirements,
and based on these requirements, identify where QoS classification and marking mechanisms
should be applied. You will discuss your solution with the instructor and other classmates, and
the instructor will present a solution for the case study to the class.
Task 1: Classification and Marking
The activity includes these tasks:
Step 1
Review customer QoS requirements: Completely read the customer requirements
provided.
This case study involves analyzing an administrative QoS policy of the JC Whitney
Corporation, a fictitious manufacturer of medical equipment. The company has
provided you with a brief description of their requirements. It is your task to provide
the network engineers from JC Whitney with a QoS solution to meet their
requirements.
Read the customer requirements and discuss them with your partner. Identify the
different types of traffic in use in the JC Whitney network and the different service
classes required to implement their administrative QoS policy.
Company Background
JC Whitney Corporation is a leading manufacturer of medical equipment used in outpatient
surgical centers throughout the United States. The company headquarters are located in
Eugene, Oregon.
In addition to the headquarters facility, JC Whitney consists of five manufacturing facilities and
120 regional sales and distribution centers. The network at each of the manufacturing facilities
is similar to the JC Whitney corporate network. The regional sales and distribution centers are
very low-cost, low-overhead sites.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
47
JC Whitney Regional Sales Office Network
© 2006 Cisco Systems, Inc. All rights reserved.
QoS v2.2—17
The regional sales and distribution center networks are shown in the figure.
The manufacturing strategy of JC Whitney is to leverage the expertise of contract
manufacturers through its extensive extranet of partners. Currently, the JC Whitney extranet
consists of nine contract manufacturers and suppliers that are all connected using a national
service provider backbone.
48
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
JC Whitney Extranet Network
© 2006 Cisco Systems, Inc. All rights reserved.
QoS v2.2—14
The service provider currently uses MPLS on its backbone as shown in the figure.
Customer Situation
JC Whitney has recently opened up Internet access to its regional manufacturing facilities and
to its regional sales and distribution centers. As a result, access times to many of the company
mission-critical applications such as sales and manufacturing databases have increased
dramatically. In addition, response time between the corporate headquarters and JC Whitney
extranet partners has increased, causing database queries to time out in some instances. No new
applications have been added to the network other than enabling corporate-wide Internet
access.
The JC Whitney network engineering staff explains their network applications in this manner:
JC Whitney has standardized on OSPF as its routing protocol and therefore uses it on all
routers company-wide.
The corporate headquarters and the five manufacturing facilities use VoIP for all intrasite
and intersite communications.
The entire ERP database for the company is located at the corporate site. All sites
(manufacturing, regional sales and distribution centers, and extranet partners), use this
centralized database for inventory control, sales data, invoicing, and so on. Without
complete access and reachability to the ERP database and its applications, JC Whitney
could not manufacture product, ship inventory, or bill for its services.
E-mail is another application that is used heavily at JC Whitney. The exchange servers and
mail gateways are all located in the server farm at the corporate headquarters location.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
49
Internet services have recently been introduced company-wide. One of its largest uses has
been messaging between regional sales and distribution centers and between corporate staff
and manufacturing. No internal messaging service currently exists at JC Whitney. As a
result, the productivity gains realized by this Internet service have become somewhat
important to the company. No other business applications currently exist on the Internet.
Although the JC Whitney manufacturing facilities operate 24 hours per day, seven days per
week, the evening shifts have a reduced staff and line output. As a result, database
synchronization and server backups are performed during the evening hours. A TCP-based
backup application manages file transfers between manufacturing sites and the corporate
headquarters using an automated version of FTP. Database synchronization is also TCPbased and has no critical bandwidth or latency requirements.
Working with the network engineering staff at JC Whitney and the service provider, you have
been enlisted to assist JC Whitney by defining QoS requirements for their network. Their first
priority is to determine what service classes to use and to identify where QoS classification and
marking mechanisms should be configured in the network to enable the JC Whitney
administrative QoS policy, resolving the response time issues that they are experiencing.
Step 2
Identify QoS service class requirements: With the aid of your partner, identify the
service classes required to implement the administrative QoS policy based on
customer requirements.
Identify the different service classes required to implement the JC Whitney
administrative QoS policy. Use the QoS Service Classes table to help you with your
answer choices. Write your answers in the table below.
JC Whitney Service Classes
Customer Traffic
50
Service Class
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
QoS Service Classes
PHB
DSCP
DSCP
Value
Intended
Protocols and
Applications
Service
Class
EF
EF
101110
Interactive voice
Voice Bearer
AF1
AF11
AF12
AF13
001010
001100
001110
Intranet, general data
service
Bulk Data
AF2
AF21
AF22
AF23
010010
010100
010110
Database access,
transaction services,
interactive traffic,
preferred data service
Transactional
AF3
AF31
AF32
AF33
011010
011100
011110
Locally defined
mission-critical
applications
MissionCritical
AF4
AF41
AF42
AF43
100010
100100
100110
Interactive video and
associated voice
Interactive
Video
CS6
Class 6
110000
Border Gateway
Protocol (BGP),
OSPF, etc.
Routing
(Reserved)
CS4
Class 4
100000
Often proprietary
Streaming
Video
CS3
Class 3
011000
Session initiation
protocol (SIP), H.323,
etc.
Voice
Signaling
CS1
Class 1
001000
User-selected service,
point-to-point
applications
Default
Default
(BestEffort)
Class 0
000000
Unspecified traffic, email
Less-thanBest Effort
Data
(Scavenger)
Best-Effort
Service Class and
Configuration
Admission Control = RSVP
Queuing = Priority
Queuing = Rate Based
Active Queue Mgt = WRED
minth AF13 < maxth AF13 <=
minth AF12 < maxth AF12 <=
minth AF11 < maxth AF11
Queuing = Rate Based
Active Queue Mgt = WRED
minth AF23 < maxth AF23 <=
minth AF22 < maxth AF22 <=
minth AF21 < maxth AF21
Queuing = Rate Based
Active Queue Mgt = WRED
minth AF33 < maxth AF33 <=
minth AF32 < maxth AF32 <=
minth AF31 < maxth AF31
Admission Control = RSVP
Queuing = Rate Based
Active Queue Mgt = WRED
minth AF43 < maxth AF43 <=
minth AF42 < maxth AF42 <=
minth AF41 < maxth AF41
Queuing = Rate Based
Small guaranteed minimum rate
Active Queue Mgt = RED
minth < maxth, but minth is
deep to minimize loss
Admission Control = RSVP
Queuing = Rate Based
Active Queue Mgt = RED
minth < maxth
Queuing = Rate Based
Small guaranteed minimum rate
Active Queue Mgt = RED
minth < maxth, but minth is
deep to minimize loss
Queuing = Rate Based
No bandwidth guarantee
Active Queue Mgt = RED
minth < maxth
Queuing = Rate Based
Minimal bandwidth guarantee
Active Queue Mgt or Per-flow
fair queuing
Active Queue Mgt = RED
minth < maxth
In order to provide end-to-end QoS, multiple markers may be required. For each service class
required for the JC Whitney network, complete the table below with the appropriate value of
each specified marker.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
51
JC Whitney QoS Service Class Requirements
L 3 Classification
Service Class
Step 3
DSCP PHB
DSCP
IP Precedence
L 2 Classification
CoS
MPLS EXP
Identify network locations where classification and marking should be applied:
Identify locations in the network where the QoS classification and marking
mechanisms should be applied to properly implement the administrative QoS policy.
Using the information provided in the review of customer QoS requirements for this
case study; use the diagrams of the JC Whitney network below to indicate trust
boundaries, where classification and marking should be applied, markers in use, and
locations where QoS markers change to ensure end-to-end QoS. Use the example
shown to assist you in completing this activity. Indicate the following on the
network diagram provided:
52
Trust boundaries
QoS markers in use
Network locations where classification and marking should be used
Locations where QoS markers change
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Example Network
© 2006 Cisco Systems, Inc. All rights reserved.
QoS v2.2—15
The figure illustrates a sample network showing trust boundaries, where classification and
marking should be applied, and markers in use.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
53
JC Whitney Corporate Headquarters Network
The JC Whitney network consists of a converged voice and data network. Because voice is a
business-critical application, all voice traffic should be treated appropriately. The user
community at JC Whitney ranges from novice data-entry clerks to advanced systems
programmers. As a result, security measures require that user workstations should not be
allowed to set packet priorities.
JC Whitney Corporate Network
© 2006 Cisco Systems, Inc. All rights reserved.
QoS v2.2—16
Use the network diagram of the JC Whitney corporate network to indicate the following:
54
Trust boundaries
QoS markers in use
Network locations where classification and marking should be used
Locations where QoS markers change
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
JC Whitney Regional Sales and Distribution Center Networks
The JC Whitney regional sales and distribution center networks are very low-overhead
operations. Each sales office is staffed with three to nine employees. Distribution centers are
similar to sales offices, but can be supported by up to 20 employees. The network at each center
consists of a basic 10/100 Mbps desktop switch that is used to connect the office workstations
to the corporate headquarters or a regional manufacturing facility via a Frame Relay-connected
low-end router.
JC Whitney Regional Sales Office Network
© 2006 Cisco Systems, Inc. All rights reserved.
QoS v2.2—17
Use the network diagram of the JC Whitney corporate network to indicate the following:
Trust boundaries
QoS markers in use
Network locations where classification and marking should be used
Locations where QoS markers change
Step 4
Present your solution: Together with your partner, present your solution to the
class. Include this information:
Customer service class requirements
Network diagrams indicating where classification and marking should be applied
Justification for differences from the solution presented by the instructor
Activity Verification
You have completed this activity when the instructor has verified your case study solution and
you have justified major deviations from the solution supplied by the instructor.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
55
Case Study 4-1 Answer Key: Classification and Marking
Identify QoS Service Class Requirements
JC Whitney Service Classes
Customer Traffic
Service Class
OSPF Routing Protocol
Reserved
Voice over IP
Voice Bearer
Voice Signaling (Skinny, SIP, etc.)
Voice Signaling
ERP (Transactional Database)
Transactional Data
E-mail
Best-Effort Data
Internet (Browsing, Messaging)
Bulk Data
Backup, Synch (FTP Bulk transfer)
Bulk Data
JC Whitney QoS Service Class Requirements
L 3 Classification
Service Class
DSCP PHB
DSCP
IP Precedence
CoS
MPLS EXP
CS 6
48 (110 000)
6
6
6
EF
46 (101 110)
5
5
5
Voice Signaling
CS3
24 (011 000)
3
3
3
Transactional Data
AF21
18 (010 010)
2
2
2
Bulk Data
AF11
10 (001 010)
1
1
1
Default
0 (000 000)
0
0
0
Reserved
Voice Bearer
Best-Effort Data
56
L 2 Classification
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Identify Network Locations Where Classification and Marking Should be Applied
Case Study Results:
JC Whitney Service Classes
© 2006 Cisco Systems, Inc. All rights reserved.
QoS v2.2—18
Case Study Results:
QoS Service Class Requirements
© 2006 Cisco Systems, Inc. All rights reserved.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
QoS v2.2—19
Lab Guide
57
Case Study Results:
JC Whitney Corporate Network
© 2006 Cisco Systems, Inc. All rights reserved.
QoS v2.2—20
Case Study Results:
JC Whitney Regional Sales Office Network
© 2006 Cisco Systems, Inc. All rights reserved.
58
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
QoS v2.2—21
© 2006 Cisco Systems, Inc.
Lab 4-1: Classification and Marking Using MQC
Complete this lab activity to practice what you learned in the lesson “Using MQC for ClassBased Marking” in the module “Classification and Marking.”
Activity Objective
In this activity, you will configure classification using MQC and marking using class-based
marking. After completing this activity, you will be able to meet these objectives:
Configure an IP extended access list matching specific traffic for use in MQC classification
Configure MQC classification
Configure class-based marking
Visual Objective
The figure illustrates what you will accomplish in this activity.
From the AutoQoS results, the E-Commerce University IT staff has determined that the VoIP
voice quality is now satisfactory. Because you did such a great job so far, the E-Commerce
University is now calling upon you to also improve the response time of the Oracle (SQL)
student administration database application over their spring break. Because AutoQoS only
works for voice traffic currently, you decide to remove the AutoQoS configurations and to
manually implement the proper QoS mechanisms using MQC.
As you have learned in the Cisco QoS course, one of the first steps to implement QoS is to
properly classify and mark the traffic. Therefore, you decide the first step now for you is to
implement the proper classification and marking.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
59
To ease into the QoS implementation, you decide to first approach the classification and
marking of the applications you feel are the bulk of the university traffic (FTP and HTTP).
Required Resources
These are the resources and equipment required to complete this activity:
Lab topology configured for QoS
Student workgroup consisting of two user-controlled Cisco 2610XM routers and one usercontrolled Cisco 2950T-24 workgroup switch
Classroom reference materials as follows:
—
QoS Student Guide
—
QoS Lab Guide
Student pod workstation with Telnet or console access to workstation pod devices
Command List
The table describes the commands used in this activity.
Classification and Marking Using MQC Lab Commands
60
Command
Description
access-list access-listnumber {deny | permit} tcp
src src-wildcard [operator
[port]] dest dest-wildcard
[operator [port]]
Defines an extended IP access list for TCP-based traffic
class-map class-map-name
Creates a class map to be used for matching packets to a
specified class
match access-group {accessgroup | name access-groupname}
Configures the match criteria for a class map on the basis of the
specified ACL
policy-map policy-map-name
Creates or modifies a policy map that can be attached to one or
more interfaces
class {class-name | classdefault}
Specifies the name of the class whose policy you want to create
or change or specifies the default class
set dscp dscp-value
Marks a packet by setting the DSCP
service-policy {input |
output} policy-map-name
Attaches a policy map to an input interface or VC, or an output
interface or VC
show access-lists [accesslist-number | access-listname]
Displays the contents of current access lists
show class-map [class-mapname]
Displays all class maps and their matching criteria
show policy-map [policy-map]
Displays the configuration of all classes for a specified service
policy map or all classes for all existing policy maps
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Command
Description
show policy-map interface
interface-name [input |
output] [class class-mapname]
Displays the packet statistics of all classes that are configured for
all service policies on the specified interface or subinterface
copy running-config startupconfig
Saves your entries in the configuration file
Job Aid
This job aid is available to help you complete the lab activity.
Your assigned workgroup pod number provided by the instructor.
Task 1: IP Extended Access List
You will configure an IP extended access list matching specific traffic for use in MQC
classification.
Activity Procedure
Complete these steps:
Step 1
Connect to the WGxR1 router. Configure an IP extended access list to match all FTP
traffic.
Step 2
On the WGxR1 router, configure a second IP extended access list to match all HTTP
(WWW) traffic.
Step 3
Display and verify your IP extended access list configuration.
Extended IP access list 101
10 permit tcp any any eq ftp
20 permit tcp any any eq ftp-data
Extended IP access list 102
10 permit tcp any any eq www
Activity Verification
You have completed this task when you attain this result:
You have configured an IP extended access list matching specific traffic for use in MQC
classification.
Task 2: Configure MQC Classification
You will configure MQC classification.
Activity Procedure
Complete these steps:
Step 1
Create two new class maps called match-ftp and match-www to match the FTP and
WWW traffic, respectively.
Step 2
Display and verify your class-map configuration.
Class Map match-any class-default (id 0)
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
61
Match any
Class Map match-all match-ftp (id 1)
Match access-group 101
Class Map match-all match-www (id 2)
Match access-group 102
62
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Activity Verification
You have completed this task when you attain this result:
You have configured MQC classification.
Task 3: Configure Class-Based Marking
You will configure class-based marking.
Activity Procedure
Complete these steps:
Step 1
Create a policy map on your workgroup WGxR1 router, named mark-apps, that
includes the two newly configured traffic classes (match-ftp and match-www). Use
class-based marking to mark the FTP traffic to AF 11 and the WWW traffic to DSCP 0.
Step 2
Display and verify your policy-map configuration.
Policy Map mark-apps
Class match-ftp
set dscp af11
Class match-www
set dscp default
Step 3
Apply the policy map to the FastEthernet 0/0 interface of your WGxR1 router in the
inbound direction.
Step 4
Display and verify your service policy.
FastEthernet0/0
Service-policy input: mark-apps
Class-map: match-ftp (match-all)
320 packets, 19200 bytes
5 minute offered rate 1000 bps, drop rate 0 bps
Match: access-group 101
QoS Set
dscp af11
Packets marked 320
Class-map: match-www (match-all)
172 packets, 10320 bytes
5 minute offered rate 1000 bps, drop rate 0 bps
Match: access-group 102
QoS Set
dscp default
Packets marked 172
Class-map: class-default (match-any)
12591 packets, 827819 bytes
5 minute offered rate 26000 bps, drop rate 0 bps
Match: any
Step 5
Step 6
How many packets have been matched and marked on WGxR1 for each traffic class?
Class ftp
__________________
Class www
__________________
Class class-default
__________________
Repeat Steps 1 through 9 for workgroup router WGxR2.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
63
Step 7
Step 8
How many packets have been matched and marked on WGxR2 for each traffic class?
Class ftp
__________________
Class www
__________________
Class class-default
__________________
Save your running configurations of the workgroup routers and the workgroup switch
to the startup-config in NVRAM.
Activity Verification
You have completed this task when you attain these results:
You have correctly created MQC classification for FTP and HTTP traffic.
You have correctly configured MQC marking to mark FTP traffic as AF11 and HTTP
traffic as DSCP 0.
You have correctly enabled MQC classification and marking by applying the service policy
to both workgroup routers.
Lab 4-1 Answer Key: Classification and Marking Using MQC
When you complete this activity, your router configuration will be similar to the following,
with differences that are specific to your device or workgroup.
access-list 101 permit tcp any any eq ftp
access-list 101 permit tcp any any eq ftp-data
access-list 102 permit tcp any any eq www
class-map match-all
match access-group
class-map match-all
match access-group
match-www
102
match-ftp
101
policy-map mark-apps
class match-ftp
set dscp af11
class match-www
set dscp default
interface FastEthernet0/0
service-policy input mark-apps
64
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Lab 4-2: Classification Using NBAR
Complete this lab activity to practice what you learned in the lesson “Using NBAR for
Classification” in the module “Classification and Marking.”
Activity Objective
In this activity, you will configure classification using NBAR. After completing this activity,
you will be able to meet these objectives:
Discover network applications and traffic using NBAR protocol discovery
Configure class-based marking using NBAR classification
Visual Objective
The figure illustrates what you will accomplish in this activity.
After studying your current classification and marking strategy, you realize that using extended
IP access lists cannot properly classify all the traffic now running on the network. One issue is
that there are too many applications being classified into the class-default. Therefore, you
decide to configure NBAR for your classification requirements. Before you configure protocol
matching with NBAR, you decide first to analyze the network using NBAR protocol discovery
to validate your assumptions about the traffic currently traversing the network. After all traffic
has been properly identified, you plan to configure a new class-based marking policy to classify
and mark the applications running on the network.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
65
Required Resources
These are the resources and equipment required to complete this activity:
Lab topology configured for QoS
Student workgroup consisting of two user-controlled Cisco 2610XM routers and one usercontrolled Cisco 2950T-24 workgroup switch
Classroom reference materials as follows:
—
QoS Student Guide
—
QoS Lab Guide
Student pod workstation with Telnet or console access to workstation pod devices
Command List
The table describes the commands used in this activity.
Classification and Marking Using NBAR Lab Commands
66
Command
Description
no service-policy {input |
output} policy-map-name
Removes a service policy from an input or output interface
[no] ip nbar protocoldiscovery
Configures NBAR to discover traffic for all protocols known to
NBAR on a particular interface
show ip nbar protocoldiscovery [interface
interface-spec]
Displays the statistics gathered by the NBAR protocol discovery
feature
clear ip nbar protocoldiscovery
Clears NBAR protocol discovery statistics
ip access-list {standard |
extended} access-list-name
Defines an IP access list by name
permit tcp source sourcewildcard destination
destination-wildcard
[operator [port]]
Sets conditions to allow a packet to pass a named IP access list
permit udp source sourcewildcard destination
destination-wildcard
[operator [port]]
Sets conditions to allow a packet to pass a named IP access list
class-map class-map-name
Creates a class map to be used for matching packets to a
specified class
match protocol protocol-name
Configures the match criteria for a class map on the basis of the
specified protocol
match access-group {accessgroup | name access-groupname}
Configures the match criteria for a class map on the basis of the
specified ACL
policy-map policy-map-name
Creates or modifies a policy map that can be attached to one or
more interfaces
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Command
Description
class {class-name | classdefault}
Specifies the name of the class whose policy you want to create
or change or specifies the default class
set dscp dscp-value
Marks a packet by setting the DSCP
service-policy {input |
output} policy-map-name
Attaches a policy map to an input interface or VC, or an output
interface or VC
show class-map [class-mapname]
Displays all class maps and their matching criteria
show policy-map [policy-map]
Displays the configuration of all classes for a specified service
policy map or all classes for all existing policy maps
show policy-map interface
interface-name [input |
output] [class class-mapname]
Displays the packet statistics of all classes that are configured for
all service policies on the specified interface or subinterface
copy running-config startupconfig
Saves your entries in the configuration file
Job Aid
This job aid is available to help you complete the lab activity.
Your assigned workgroup pod number provided by the instructor
Task 1: Discover Applications and Traffic Using NBAR
You will discover network applications and traffic using NBAR protocol discovery.
Activity Procedure
Complete these steps:
Step 1
Disable the existing inbound service policy on the FastEthernet 0/0 interface of your
WGxR1 router.
Step 2
Verify that Cisco Express Forwarding is enabled on your WGxR1 router.
Step 3
Enable NBAR protocol discovery on the FastEthernet 0/0 interface of your WGxR1
router.
Step 4
Clear the NBAR protocol discovery counters on WGxR1.
Step 5
Wait for the interface counters to accumulate traffic statistics for at least one minute.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
67
Step 6
Display the NBAR protocol discovery traffic statistics of all NBAR discovered
protocols.
FastEthernet0/0
Input
Packet Count
Byte Count
5 minute bit rate (bps)
--------------- -----------------------sqlnet
157
9420
1000
citrix
201
13642
1000
http
86
13353
0
napster
98
5880
0
Protocol
Output
Packet Count
Byte Count
5 minute bit rate (bps)
-----------------------404
60678
3000
547
51549
3000
255
59838
3000
272
54727
3000
[rest omitted]
Step 7
In the space provided below, list the protocols discovered by NBAR protocol
discovery:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
Step 8
Disable NBAR protocol discovery from the FastEthernet 0/0 interface on WGxR1.
Step 9
Repeat Steps 1 through 8 for workgroup router WGxR2.
Activity Verification
You have completed this task when you attain this result:
68
You have properly configured NBAR protocol discovery to identify network applications.
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Task 2: Configure Classification Using NBAR
You will configure classification of discovered applications using NBAR classification.
Activity Procedure
Complete these steps:
Step 1
Note
On the WGxR1 router, configure NBAR classification and MQC marking to classify
inbound traffic on the FastEthernet 0/0 interface and mark it as outlined in the table
below. Completion of this lab step will require the configuration of five new class
maps (one for each service class) and the configuration of a policy map (called marknbar) that marks traffic in each class appropriately.
Remember that by default a class map is set to match all. If you are matching multiple
protocols in the same class, remember to use match-any instead of match-all.
Class Name
(class-map name)
Protocol
PHB
real-time
rtp/rtcp
EF
real-time
icmp
EF
mission-critical
sqlnet
AF 31
voice-control (port specific
tcp and udp)
interactive
citrix
AF 21
bulk
ftp
AF 11
scavenger
kazaa2
CS 1
scavenger
napster
CS 1
class-default
all others
BE
When using NBAR to match RTP packets, one limitation is that protocol matching
for RTP does not match control packets. This is somewhat of an advantage in that it is
preferred that voice bearer traffic be separated from voice control traffic because each
traffic type receives different QoS treatment (EF for voice bearer and AF31 for voice
control).
Create the following named access list for matching RTCP traffic:
ip access-list extended VoIP-RTCP
permit udp any any range 16384 32767
Match the named access list, VoIP-RTCP, into the real-time traffic class along with
the RTP and ICMP traffic.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
69
The mission-critical class should be configured to contain both the sqlnet traffic and
voice-control traffic. Use this ACL to match voice control traffic when creating the
mission-critical class on your router:
ip access-list extended Voice-Control
permit tcp any any eq 1720
permit tcp any any range 11000 11999
permit udp any any eq 2427
permit tcp any any eq 2428
permit tcp any any range 2000 2002
permit udp any any eq 1719
permit udp any any eq 5060
Note
Step 2
Recall that ICMP traffic has been placed in the real-time class as a means of measuring
QoS performance.
Display and verify your class map configuration.
Class Map match-all bulk (id 8)
Match protocol ftp
Class Map match-any real-time (id 5)
Match protocol rtp
Match protocol icmp
Match access-group name VoIP-RTCP
Class Map match-any mission-critical (id 6)
Match protocol sqlnet
Match access-group name Voice-Control
Class Map match-all interactive (id 7)
Match protocol citrix
Class Map match-any scavenger (id 9)
Match protocol kazaa2
Match protocol napster
[rest omitted]
Step 3
Display and verify your policy map configuration.
Policy Map mark-nbar
Class real-time
set dscp ef
Class mission-critical
set dscp af31
Class interactive
set dscp af21
Class bulk
set dscp af11
Class scavenger
set dscp cs1
Class class-default
set dscp default
70
Step 4
Apply the policy map to the FastEthernet 0/0 interface of your WGxR1 router in the
inbound direction.
Step 5
Wait for the interface counters to accumulate traffic statistics for at least one minute.
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Step 6
Display and verify your service policy on interface FastEthernet 0/0.
FastEthernet0/0
Service-policy input: mark-nbar
Class-map: real-time (match-any)
542 packets, 115388 bytes
5 minute offered rate 4000 bps, drop rate 0 bps
Match: protocol rtp
4 packets, 856 bytes
5 minute rate 0 bps
Match: protocol icmp
1 packets, 70 bytes
5 minute rate 0 bps
Match: access-group name AutoQoS-VoIP-RTCP
537 packets, 114462 bytes
5 minute rate 4000 bps
QoS Set
dscp ef
Packets marked 542
Class-map: mission-critical (match-any)
366 packets, 54424 bytes
5 minute offered rate 4000 bps, drop rate 0 bps
Match: protocol sqlnet
331 packets, 50194 bytes
5 minute rate 3000 bps
Match: access-group name Voice-Control
35 packets, 4230 bytes
5 minute rate 2000 bps
QoS Set
dscp af31
Packets marked 366
Class-map: interactive (match-all)
262 packets, 15720 bytes
5 minute offered rate 2000 bps, drop rate 0 bps
Match: protocol citrix
QoS Set
dscp af21
Packets marked 295
[rest omitted]
Step 7
Note
Step 8
How many packets have been matched and marked for each of the traffic classes?
Class real-time
_______________________________
Class mission-critical
_______________________________
Class interactive
_______________________________
Class bulk
_______________________________
Class scavenger
_______________________________
Class class-default
_______________________________
If the real-time, mission-critical, and scavenger classes have no matches, verify your classmap configuration to ensure they are set to match-any and not match-all.
Repeat Steps 1 through 6 for workgroup router WGxR2.
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
71
Step 9
How many packets have been matched and marked for each of the traffic classes?
Class real-time
_______________________________
Class mission-critical
Class interactive
_______________________________
_______________________________
Class bulk
_______________________________
Class scavenger
_______________________________
Class class-default
Step 10
_______________________________
Save your running configurations of the workgroup routers and the workgroup switch
to the startup-config in NVRAM.
Activity Verification
You have completed this task when you attain these results:
You have correctly configured NBAR classification.
You have correctly configured class-based marking of NBAR classified traffic.
Lab 4-2 Answer Key: Classification Using NBAR
When you complete this activity, your router configuration will be similar to the following,
with differences that are specific to your device or workgroup.
WG1R1(config)#int fa 0/0
WG1R1(config-if)#no service-policy input mark-apps
WG1R1(config-if)#ip nbar protocol-discovery
NBAR should have discovered the following protocols:
HTTP
citrix
sqlnet
napster
netbios
FTP
exchange
kazaa2
LDAP
RTP
Unknown
ip access-list extended VoIP-RTCP
permit udp any any range 16384 32767
!
ip access-list extended Voice-Control
permit tcp any any eq 1720
permit tcp any any range 11000 11999
permit udp any any eq 2427
permit tcp any any eq 2428
permit tcp any any range 2000 2002
permit udp any any eq 1719
permit udp any any eq 5060
!
class-map match-all bulk
match protocol ftp
class-map match-any real-time
72
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
match protocol rtp
match protocol icmp
match access-group name VoIP-RTCP
class-map match-any mission-critical
match protocol sqlnet
match access-group name Voice-Control
class-map match-all interactive
match protocol citrix
class-map match-all default
match any
class-map match-any scavenger
match protocol kazaa2
match protocol napster
!
policy-map mark-nbar
class real-time
set dscp ef
class mission-critical
set dscp af31
class interactive
set dscp af21
class bulk
set dscp af11
class scavenger
set dscp cs1
class class-default
set dscp default
!
interface FastEthernet0/0
service-policy input mark-nbar
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
73
Lab 4-3: Configuring QoS Preclassify
Complete this lab activity to practice what you learned in the lesson “Configuring QoS
Preclassify” in the module “Classification and Marking.”
Activity Objective
In this activity, you will configure and examine QoS preclassify. After completing this activity,
you will be able to meet these objectives:
Configure a GRE tunnel
Configure QoS preclassify on a Cisco IOS router using a GRE tunnel
Monitor QoS preclassify configurations
Visual Objective
The figure illustrates what you will accomplish in this activity.
The E-Commerce University IT staff has decided to implement a GRE tunnel between the
north and south campus via the existing 768-kbps Internet connection. After the GRE tunnel is
set up and working properly, IPSec will also be enabled over the GRE tunnel. At this point, the
E-Commerce University IT staff needs you to first configure and test the GRE tunnel (without
IPSec). The university plans to send different types of traffic over the tunnel and would like to
be able to differentiate between different traffic flows so that QoS can be applied. In this lab,
you will configure and verify the QoS preclassify feature for traffic classification over a GRE
tunnel.
74
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Required Resources
These are the resources and equipment required to complete this activity.
Lab topology configured for QoS
Student workgroup consisting of two user-controlled Cisco 2610XM routers and one usercontrolled Cisco 2950T-24 workgroup switch
Classroom reference materials as follows:
—
QoS Student Guide
—
QoS Lab Guide
Student pod workstation with Telnet or console access to workstation pod devices
Command List
The table describes the commands used in this activity.
Configuring VPN QoS Lab Commands
Command
Description
interface interface-id
Enters interface configuration mode and the physical interface
identification
qos pre-classify
Enables QoS preclassification
ip cef
Enables CEF on the router
[no] shutdown
Disables an interface
show ip interface [brief]
[type] [number]
Lists a summary of an interface IP information and status
copy running-config startupconfig
Saves your entries in the configuration file
Job Aid
This job aid is available to help you complete the lab activity.
Your assigned workgroup pod number provided by the instructor
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
75
Task 1: Configure GRE Tunnel
You will configure a GRE tunnel.
Activity Procedure
Complete these steps:
Step 1
Verify that the S0/0 and S0/1 interfaces of your workgroup WGxR1 and WGxR2
routers are UP.
WGxR1#show ip interface brief
Interface
IP-Address
OK? Method Status
Protocol
FastEthernet0/0
10.3.x.2
YES NVRAM
up
up
Serial0/0
10.2.x.2
YES unset
up
Serial0/1
10.5.x.2
YES NVRAM
up
up
up
Step 2
Verify that CEF switching is still enabled on both workgroup routers in your pod.
Step 3
Configure a GRE tunnel between your WGxR1 and WGxR2 routers via the service
provider core as follows:
! WGxR1
!
interface Tunnel0
ip unnumbered fastethernet0/0
tunnel source Serial0/1
tunnel destination 10.5.x.2
! WGxR2
!
interface Tunnel0
ip unnumbered fastethernet0/0
tunnel source Serial0/1
tunnel destination 10.4.x.1
Step 4
Configure a static route via the tunnel 0 interface to the 10.1.x.0 or 10.3.x.0 subnet
on the respective WGxR router as follows:
! WGxR1
!
ip route 10.3.x.0 255.255.255.0 Tunnel0
! WGxR2
!
ip route 10.1.x.0 255.255.255.0 Tunnel0
76
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Step 5
Display the tunnel interface and verify that it is UP and operational.
WGxR2#show interface tunnel 0
Tunnel0 is up, line protocol is up
Hardware is Tunnel
Interface is unnumbered. Using address of FastEthernet0/0 (10.3.x.2)
MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,
reliability 255/255, txload 81/255, rxload 196/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel source 10.5.x.2 (Serial0/1), destination 10.4.x.1
Tunnel protocol/transport GRE/IP, key disabled, sequencing disabled
Tunnel TTL 255
Checksumming of packets disabled, fast tunneling enabled
Last input 00:00:03, output 00:00:04, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 25000 bits/sec, 9 packets/sec
5 minute output rate 39000 bits/sec, 23 packets/sec
87865 packets input, 12254589 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
282049 packets output, 54114890 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
Step 6
Use Telnet to connect to the Callgen-1 (10.1.x.11) router and perform a traceroute to
the Callgen-2 (10.3.x.11) router. Verify that the path goes thru your GRE tunnel.
Callgen-1>traceroute 10.3.x.11
Type escape sequence to abort.
Tracing the route to 10.3.x.11
1 10.1.x.1 4 msec 0 msec 0 msec
2 10.3.x.11 140 msec * 8 msec
Step 7
Use Telnet to connect to the Callgen-2 router and perform a traceroute to the
Callgen-1 router. Verify that the path goes through your GRE tunnel.
Callgen-2>traceroute 10.1.x.11
Type escape sequence to abort.
Tracing the route to 10.1.x.11
1 10.3.x.2 60 msec 56 msec 64 msec
2 10.1.x.11 60 msec * 56 msec
Step 8
Issue the show queue serial0/1 command to display the WFQ information for the
serial 0/1 interface.
WGxR1#show queue serial0/1
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 9269
Queueing strategy: weighted fair
Output queue: 42/1000/64/9269 (size/max total/threshold/drops)
Conversations
1/31/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 576 kilobits/sec
(depth/weight/total drops/no-buffer drops/interleaves) 41/32384/9269/0/0
Conversation 95, linktype: ip, length: 206
source: 10.5.8.2, destination: 10.4.8.1, id: 0xC2FA, ttl: 255, prot: 47
© 2006 Cisco Systems, Inc.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Lab Guide
77
You may have to run the show queue interface command a few times until you catch an
active flow. If you are not able to see packets in the queue after several attempts, log onto
your other workgroup router and repeat Step 8.
Note
How many active flows does the router see? ____________________________
Notice that when QoS preclassify is not configured, the output interface sees only one flow,
which is Protocol 47 (GRE).
Activity Verification
You have completed this task when you attain this result:
You have successfully configured a tunnel interface between WGxR1 and WGxR2 through
the service provider backbone.
Task 2: Configure QoS Preclassify
You will configure QoS preclassify on a Cisco IOS router.
Activity Procedure
Complete this step:
Step 1
Configure the QoS preclassify feature on the tunnel interface.
Activity Verification
You have completed this task when you attain this result:
78
You have successfully enabled the QoS preclassify feature on the tunnel interface.
Implementing Cisco Quality of Service (QOS) v2.2
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
© 2006 Cisco Systems, Inc.
Task 3: Monitor QoS Preclassify
You will monitor QoS preclassify operations.
Activity Procedure
Complete these steps:
Step 1
Issue the show queue serial0/1 command again to display the WFQ information for
the serial 0/1 interface.
WGxR1#show queue serial0/1
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 117791
Queueing strategy: weighted fair
Output queue: 157/1000/64/117791 (size/max total/threshold/drops)
Conversations
21/31/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 576 kilobits/sec
(depth/weight/total drops/no-buffer drops/interleaves) 7/32384/0/0/0
Conversation 119, linktype: ip, length: 72
source: 10.1.1.10, destination: 10.3.1.10, id: 0xFF4C, ttl: 254,
TOS: 104 prot: 6, source port 1063, destination port 1521
(depth/weight/total drops/no-buffer drops/interleaves) 7/32384/0/0/0
Conversation 212, linktype: ip, length: 196
source: 10.1.1.10, destination: 10.3.1.10, id: 0xE642, ttl: 127,
TOS: 72 prot: 6, source port 1102, destination port 1494
(depth/weight/total drops/no-buffer drops/interleaves) 7/32384/0/0/0
Conversation 64, linktype: ip, length: 79
source: 10.1.1.10, destination: 10.3.1.10, id: 0x908A, ttl: 126,
TOS: 184 prot: 17, source port 49590, destination port 49602