Enterprise QoS Solution Reference Network Design Guide

More documents

Recommendations

Info

Catalyst 6500 PFC2/PFC3—QoS Considerations and Design 2-98 Enterprise QoS Solution Reference Network Design Guide Chapter 2 Campus QoS Design ! Binds ACL to policer and marks in-profile SAP to DSCP 25 CAT6500-PFC2-CATOS> (enable) CAT6500-PFC2-CATOS> (enable) set qos acl ip IPPHONE-PC-ADVANCED-3-1 dscp 18 aggregate TRANSACTIONAL-3-1 tcp any any eq 1352 ! Binds ACL to Dual-Rate policer and marks in-profile Lotus to AF21 CAT6500-PFC2-CATOS> (enable) CAT6500-PFC2-CATOS> (enable) set qos acl ip IPPHONE-PC-ADVANCED-3-1 dscp 10 aggregate BULK-3-1 tcp any any eq 143 ! Binds ACL to Dual-Rate policer and marks in-profile IMAP to AF11 CAT6500-PFC2-CATOS> (enable) set qos acl ip IPPHONE-PC-ADVANCED-3-1 dscp 10 aggregate BULK-3-1 tcp any any eq 220 ! Binds ACL to Dual-Rate policer and marks in-profile IMAP to AF11 CAT6500-PFC2-CATOS> (enable) CAT6500-PFC2-CATOS> (enable) set qos acl ip IPPHONE-PC-ADVANCED-3-1 dscp 0 aggregate PC-DATA-3-1 any ! Binds ACL to policer and marks other in-profile PC data to DSCP 0 CAT6500-PFC2-CATOS> (enable) CAT6500-PFC2-CATOS> (enable) CAT6500-PFC2-CATOS> (enable) commit qos acl IPPHONE-PC-ADVANCED-3-1 ! Commits ACL to PFC hardware CAT6500-PFC2-CATOS> (enable) CAT6500-PFC2-CATOS> (enable) set port qos 3/1 cos 0 ! Sets CoS to 0 for all untrusted packets (when there is no IP Phone on the port) CAT6500-PFC2-CATOS> (enable) set port qos 3/1 cos-ext 0 ! Sets CoS to 0 for all untrusted PC-generated packets (behind an IP Phone) CAT6500-PFC2-CATOS> (enable) set port qos 3/1 trust-ext untrusted ! Ignore any CoS values for all PC-generated packets (behind an IP Phone) CAT6500-PFC2-CATOS> (enable) set port qos 3/1 trust-device ciscoipphone ! Conditional trust (for Cisco IP Phones only) CAT6500-PFC2-CATOS> (enable) set qos acl map IPPHONE-PC-ADVANCED-3-1 3/1 ! Attaches ACL to switch port CAT6500-PFC2-CATOS> (enable) Catalyst 6500 CatOS QoS Verification Commands Catalyst 6500 CatOS QoS verification commands for the Conditionally-Trusted IP Phone + PC + Scavenger (Advanced) model include the following: show qos status show qos maps show port qos show qos acl show qos policer show qos statistics Note As previously mentioned, on non-GigabitEthernet linecards that use 2Q2T Transmit Queuing and 1Q4T Receive queuing (such as the WS-X6248-RJ-xx and the WS-X6348-RJ-xx), a hardware limitation prevents the proper functioning of port-based trust (which affects trust-cos, trust-ipprec, and trust-dscp). On such linecards, a workaround ACL can be used to achieve trust functionality. For such an example, see Catalyst 6500—Trusted Endpoint Model (Example 2-50). Version 3.3
Chapter 2 Campus QoS Design Catalyst 6500—Queuing and Dropping Version 3.3 This section includes the following topics: Catalyst 6500 Queuing and Dropping Overview Catalyst 6500 Transmit Queuing and Dropping Linecard Options Catalyst 6500—2Q2T Queuing and Dropping Catalyst 6500—1P2Q1T Queuing and Dropping Catalyst 6500—1P2Q2T Queuing and Dropping Catalyst 6500—1P3Q1T Queuing and Dropping Catalyst 6500—1P3Q8T Queuing and Dropping Catalyst 6500—1P7Q8T Queuing and Dropping Catalyst 6500 Queuing and Dropping Overview Catalyst 6500 PFC2/PFC3—QoS Considerations and Design While the Catalyst 6500 PFC performs classification, marking, mapping, and policing functions, all queuing and congestion avoidance policies are administered by the Catalyst 6500 linecards. This inevitably leads to per-linecard hardware-specific capabilities and syntax when it comes to configuring queuing and dropping. As previously discussed in relation to other platforms that support ingress queuing, receive queues are extremely difficult to congest, even in controlled lab environments. This is especially so if access edge policies, as detailed in this chapter, are used on all access layer switches. Ingress congestion implies that the combined ingress rates of traffic exceed the switch fabric channel speed, and thus would need to be queued simply to gain access to the switching fabric. On newer platforms, such as the Catalyst 6500 Sup720, this means that a combined ingress rate of up to 40 Gbps per slot would be required to create such an event. However, to obviate such an extreme event, the Catalyst 6500 schedules ingress traffic through the receive queues based on CoS values. In the default configuration, the scheduler assigns all traffic with CoS 5 to the strict-priority queue (if present); in the absence of a strict priority queue, the scheduler assigns all traffic to the standard queues. All other traffic is assigned to the standard queue(s) (with higher CoS values being assigned preference over lower CoS values, wherever supported). Additionally, if a port is configured to trust CoS, then the ingress scheduler implements CoS-value-based receive-queue drop thresholds to avoid congestion in received traffic. Thus, even if the extremely unlikely event of ingress congestion should occur, the default settings for the Catalyst 6500 linecard receive queues are more than adequate to protect VoIP and network control traffic. Therefore, the focus of this section is on Catalyst 6500 egress/transmit queuing design recommendations. Catalyst 6500 Transmit Queuing and Dropping Linecard Options There are currently six main transmit queuing/dropping options for Catalyst 6500 linecards: 2Q2T—Indicates two standard queues, each with two configurable tail-drop thresholds. 1P2Q1T—Indicates one strict-priority queue and two standard queues, each with one configurable WRED-drop threshold (however, each standard queue also has one nonconfigurable tail-drop threshold). Enterprise QoS Solution Reference Network Design Guide 2-99
Page 1 and 2:
Enterprise QoS Solution Reference N
Page 3 and 4:
Version 3.3 Preface xiii Revision H
Page 5 and 6:
Version 3.3 Enterprise QoS Solution
Page 7 and 8:
Version 3.3 Catalyst 6500 CatOS QoS
Page 9 and 10:
Version 3.3 Cisco Documentation 3-4
Page 11 and 12:
Version 3.3 QoS Baseline (11-Class)
Page 13 and 14:
Version 3.3 Preface Revision Histor
Page 15 and 16:
Preface Version 3.3 Cisco Systems A
Page 17 and 18:
Preface Version 3.3 Obtaining Addit
Page 19 and 20:
QoS Overview What is QoS? Version 3
Page 21 and 22:
Chapter 1 Quality of Service Design
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
QoS Design Overview Version 3.3 Cam
Page 55 and 56:
Chapter 2 Campus QoS Design Version
Page 57 and 58:
Chapter 2 Campus QoS Design Call Si
Page 59 and 60:
Chapter 2 Campus QoS Design Trusted
Page 61 and 62:
Page 63 and 64:
Chapter 2 Campus QoS Design Cisco I
Page 65 and 66:
Chapter 2 Campus QoS Design AutoQoS
Page 67 and 68:
Page 69 and 70:
Chapter 2 Campus QoS Design Catalys
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Chapter 2 Campus QoS Design Figure
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Chapter 2 Campus QoS Design Catalys
Page 95 and 96:
Page 97 and 98:
Page 99 and 100: Chapter 2 Campus QoS Design Catalys
Page 101 and 102: Chapter 2 Campus QoS Design Version
Page 113 and 114: Chapter 2 Campus QoS Design show ml
Page 115 and 116: Chapter 2 Campus QoS Design Figure
Page 139 and 140: Chapter 2 Campus QoS Design show qo
Page 141 and 142: Chapter 2 Campus QoS Design show qo
Page 149: Chapter 2 Campus QoS Design Version
Page 153 and 154: Chapter 2 Campus QoS Design WS-X674
Page 155 and 156: Chapter 2 Campus QoS Design Configu
Page 177 and 178: Chapter 2 Campus QoS Design Referen
Page 179 and 180: Version 3.3 WAN Aggregator QoS Desi
Page 181 and 182: Chapter 3 WAN Aggregator QoS Design
Page 201 and 202:
Chapter 3 WAN Aggregator QoS Design
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Version 3.3 Branch Router QoS Desig
Page 231 and 232:
Chapter 4 Branch Router QoS Design
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Version 3.3 MPLS VPN QoS Design CHA
Page 255 and 256:
Chapter 5 MPLS VPN QoS Design Versi
Page 257 and 258:
Chapter 5 MPLS VPN QoS Design Servi
Page 259 and 260:
Chapter 5 MPLS VPN QoS Design Call-
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Chapter 5 MPLS VPN QoS Design Short
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Chapter 5 MPLS VPN QoS Design Books
Page 287 and 288:
Version 3.3 IPSec VPN QoS Design CH
Page 289 and 290:
Chapter 6 IPSec VPN QoS Design Vers
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Chapter 6 IPSec VPN QoS Design Pref
Page 297 and 298:
Chapter 6 IPSec VPN QoS Design Dela
Page 299 and 300:
Chapter 6 IPSec VPN QoS Design QoS
Page 301 and 302:
Page 303 and 304:
Chapter 6 IPSec VPN QoS Design Anti
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Chapter 6 IPSec VPN QoS Design Digi
Page 319 and 320:
Chapter 6 IPSec VPN QoS Design DSL
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Chapter 6 IPSec VPN QoS Design Summ
Page 329 and 330:
Chapter 6 IPSec VPN QoS Design Book
show all

Enterprise QoS Solution Reference Network Design Guide

Create successful ePaper yourself

Delete template?

Save as template?