Enterprise QoS Solution Reference Network Design Guide
Enterprise QoS Solution Reference Network Design Guide
Enterprise QoS Solution Reference Network Design Guide
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Catalyst 6500 PFC2/PFC3—<strong>QoS</strong> Considerations and <strong>Design</strong><br />
2-82<br />
No ACL is mapped to port 3/1.<br />
CAT6500-PFC2-CATOS> (enable)<br />
<strong>Enterprise</strong> <strong>QoS</strong> <strong>Solution</strong> <strong>Reference</strong> <strong>Network</strong> <strong>Design</strong> <strong>Guide</strong><br />
Chapter 2 Campus <strong>QoS</strong> <strong>Design</strong><br />
On non-GigabitEthernet linecards that use 2Q2T Transmit Queuing and 1Q4T Receive queuing (such as<br />
the WS-X6248-RJ-xx and WS-X6348-RJ-xx linecards), a hardware limitation prevents the proper<br />
functioning of port-based trust (which affects trust-cos, trust-ipprec, and trust-dscp). The show port qos<br />
command can be used to determine if the linecard is a 2Q2T-Tx/1Q4T-Rx linecard. These cards also<br />
listed in Table 2-5.<br />
On such linecards, a workaround ACL can be used to achieve trust-functionality for trust-cos,<br />
trust-ipprec, and trust-dscp. The workaround ACL for trust-DSCP functionality on such linecards is<br />
shown below.<br />
Example 2-50 Trust-DSCP Workaround ACL for Catalyst 6500 2Q2T-TX/1Q4T-Rx Non-Gigabit<br />
Linecards<br />
CAT6500-PFC2-CATOS> (enable) set qos acl ip TRUST-DSCP trust-dscp any<br />
TRUST-DSCP editbuffer modified. Use 'commit' command to apply changes.<br />
CAT6500-PFC2-CATOS> (enable) commit qos acl TRUST-DSCP<br />
<strong>QoS</strong> ACL 'TRUST-DSCP' successfully committed.<br />
CAT6500-PFC2-CATOS> (enable)<br />
CAT6500-PFC2-CATOS> (enable) set qos acl map TRUST-DSCP 4/1<br />
Note To apply the <strong>QoS</strong> ACL you have defined (above), the ACL must be committed to hardware. The process<br />
of committing copies the ACL from a temporary editing buffer to the PFC hardware. Once resident in<br />
the PFC memory, the policy defined in the <strong>QoS</strong> ACL can be applied to all traffic that matches the Access<br />
Control Entries (ACEs). For ease of configuration, most administrators issue a commit all command,<br />
however you can commit a specific ACL (by name) to be sent from the editing buffer to PFC memory,<br />
as shown above.<br />
In this second example, DSCP trust is configured on a port/interface in IOS.<br />
Example 2-51 Catalyst 6500 IOS—Trusted Endpoint Example<br />
CAT6500-PFC2-IOS(config)#interface FastEthernet3/1<br />
CAT6500-PFC2-IOS(config-if)#mls qos trust dscp<br />
Other Catalyst 6500 CatOS <strong>QoS</strong> verification commands include the following:<br />
show mls qos<br />
show mls qos interface<br />
Note The ACL Trust workaround to the 2Q2T non-GigabitEthernet linecards (such as the such as the<br />
WS-X6248-RJ-xx and WS-X6348-RJ-xx) limitation of not supporting trust only applies in the access<br />
Layer of the campus (where CatOS is the recommended software for the Catalyst 6500). In the<br />
distribution and core layers, where IOS is the preferred software, all interfaces are recommended to be<br />
GigabitEthernet or higher.<br />
Catalyst 6500 Auto <strong>QoS</strong> VoIP Model<br />
At the time of writing, Auto<strong>QoS</strong> VoIP is only supported on the Catalyst 6500 in CatOS.<br />
Version 3.3
Change language