Cisco 6500 - Catalyst Series 10 Gigabit EN Interface Module Expansion White Paper - Page 4

Browse online or download pdf White Paper for Network Hardware Cisco 6500 - Catalyst Series 10 Gigabit EN Interface Module Expansion. Cisco 6500 - Catalyst Series 10 Gigabit EN Interface Module Expansion 18 pages. Distributed forwarding card 4 for ws-x68xx, ws-x69xx, and select ws-x67xx modules
Also for Cisco 6500 - Catalyst Series 10 Gigabit EN Interface Module Expansion: Installation Note (14 pages), Solution Manual (17 pages), Installation Note (46 pages), White Paper (19 pages), Description (1 pages), Product Bulletin (6 pages), Notice (4 pages), Datasheet (9 pages), Datasheet (18 pages), Configuration Manual (8 pages), Installation Note (28 pages), Troubleshooting Manual (11 pages), Installation Note (18 pages), User Manual (17 pages), Installation Note (24 pages), Manual (19 pages), Installation Note (36 pages)

Cisco 6500 - Catalyst Series 10 Gigabit EN Interface Module Expansion White Paper
Now that the major QoS groups have been explained, it is pertinent to point out where in the QoS processing path these actions take place. Figure 3
provides a high-level overview of where those actions occur.
Figure 3. Cisco Catalyst 6500 QoS Processing Model
The following section will attempt to provide some insight into the many QoS features that make up the QoS feature toolkit now available
on the Cisco Catalyst 6500.
THE QoS FEATURE TOOLKIT
The Cisco Catalyst 6500 is primed with a number of QoS features that when combined provide an effective vehicle to better service higher priority
traffic. The following section will attempt to present a high-level overview of the major QoS features in the Cisco Catalyst 6500.
Modular QoS Command-Line Interface
®
When a Cisco Catalyst 6500 runs native Cisco IOS
Software, some (not all) of the QoS configuration on the switch follows the modular QoS
command-line interface (MQC) structure that is also found in Cisco IOS Software running on Cisco routers. The normal rules of configuration
are such that a class map is built incorporating the ACLs that identify the traffic that will have QoS applied to them. The class map is then referenced
within a policy map, which contains the QoS policy that will be applied to the switch port (or VLAN). The policy is then applied to the physical or
logical interface. A high-level view of this process is shown in Figure 4.
Figure 4. MQC
© 2005 Cisco Systems, Inc. All rights reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com.
Page 4 of 18