Enterprise QoS Solution Reference Network Design Guide

Catalyst 3550—QoS Considerations and Design
2-38
Enterprise QoS Solution Reference Network Design Guide
Chapter 2 Campus QoS Design
CAT3550(config)#
CAT3550(config)#ip access list standard ANY ! Workaround ACL
CAT3550(config-std-nacl)# permit any
CAT3550(config-std-nacl)#end
CAT3550#
Catalyst MLS QoS Verification Commands
The Catalyst MLS QoS verification commands for the Conditionally-Trusted IP Phone + PC + Scavenger
(Basic) Model Configuration include the following:
show mls qos
show mls qos map
show mls qos interface
show mls qos interface policers
show mls qos statistics
show class-map
show policy-map
show policy interface
Note While Catalyst 3550 IOS syntax supports the match any criteria within a class-map (which the parser
allows to be configured in conjunction with a per-VLAN policy), testing with some versions of Catalyst
3500 IOS have revealed a limitation with this function, since it does not match any other traffic on a
per-VLAN basis. Hence an explicit access list named ANY has been used in the example above as a
workaround.
Catalyst 3550—Conditionally-Trusted IP Phone + PC with Scavenger-Class QoS
(Advanced) Model
Configuration
This section includes the following topics:
Configuration
Catalyst MLS QoS Verification Commands
The Conditionally-Trusted IP Phone + PC + Scavenger Advanced model builds on the Basic model by
including policers for PC-based video-conferencing (and/or PC SoftPhone), Mission-Critical Data
applications, Transactional Data applications, and Bulk Data applications. This model is graphically
depicted in Figure 2-9. The Catalyst 3550 can support 8 policers per 10/100 Ethernet port and so can
support this Advanced Model.
The Catalyst 3550 configuration for the Conditionally-Trusted IP Phone + PC with Scavenger-Class QoS
(Advanced) Model is shown below. In this example, the same Server-to-Client applications are used as
in the Untrusted Multi-Application Server example. However, notice that the Source/Destination ports
are reversed for the Client-to-Server direction of traffic flow. Also, due to the limit of the number of
Version 3.3