Enterprise QoS Solution Reference Network Design Guide

More documents

Recommendations

Info

Customer Edge QoS Design Considerations 5-8 Enterprise QoS Solution Reference Network Design Guide Chapter 5 MPLS VPN QoS Design that the re-marking be performed at the CE’s egress edge, not within the campus. This is because service-provider service offerings likely will evolve or expand over time, and adjusting to such changes will be easier to manage if re-marking is performed only at the CE egress edge. Additionally, in some cases, multiple types of traffic are required to be marked to the same DiffServ code point value to gain admission to the appropriate queue. For example, on high-speed links, it might be desired to send Voice, Interactive-Video, and Call-Signaling to the service provider’s Real-Time class. If this service-provider class admits only DSCP EF and CS5, two of these three applications would be required to share a common code point. The class-based marking configuration in Example 5-1 shows how this can be done (in this example, both Interactive-Video and Call-Signaling are re-marked to share DSCP CS5). Example 5-1 CE (Egress) Enterprise-to-Service Provider Re-Marking Example ! class-map match-any VOICE match ip dscp ef class-map match-all INTERACTIVE-VIDEO match ip dscp af41 class-map match-any CALL-SIGNALING match ip dscp af31 match ip dscp cs3 ! policy-map CE-EGRESS-EDGE class VOICE priority percent 18 class INTERACTIVE-VIDEO priority percent 15 set ip dscp cs5 ! Interactive-Video is remarked to CS5 class CALL-SIGNALING priority percent 2 ! Call-Signaling gets LLQ for this scenario set ip dscp cs5 ! Call-Signaling is also remarked to CS5 ! ! interface Serial1/0 service-policy output CE-EGRESS-EDGE ! Verification commands: show policy show policy interface Service providers might re-mark traffic at Layer 3 to indicate whether certain flows are out of contract. Although this is consistent with DiffServ standards, such as RFC 2597, it might present minor difficulties to enterprises that require consistent end-to-end Layer 3 marking (typically, for management or accounting purposes). In such cases, the enterprise can choose to apply re-marking policies as traffic is received back from the service provider’s MPLS VPN (on the ingress direction of the enterprise’s CE). Class-based marking can be used again because it supports not only access lists for classification, but also Network-Based Application Recognition (NBAR). Continuing and expanding on the previous example, the enterprise wants to restore the original markings that it set for Interactive-Video and Call-Signaling. Additionally, it wants to restore original markings for Oracle traffic (which it originally marked DSCP 25 and is using TCP port 9000 with) and DLSw+ traffic (originally marked AF21). Both of these data applications were handed off to the service provider marked as AF21, but they might have been marked down to AF22 within the service-provider cloud. Example 5-2 shows a configuration that enables such re-marking from the MPLS VPN. The “match-all” Version 3.3
Chapter 5 MPLS VPN QoS Design Version 3.3 Customer Edge QoS Design Considerations criteria of the class maps performs a logical AND operation against the potential markings and re-markings, and the access list (or NBAR-supported protocol) that sifts the applications apart. The policy is applied on the same CE link, but in the ingress direction. Example 5-2 CE (Ingress) Service Provider-to-Enterprise Re-Marking Example ! class-map match-all REMARKED-INTERACTIVE-VIDEO match ip dscp cs5 match access-group 101 ! Interactive-Video must be CS5 AND UDP ! class-map match-all REMARKED-CALL-SIGNALING match ip dscp cs5 match access-group 102 ! Call-Signaling must be CS5 AND TCP ! class-map match-all REMARKED-ORACLE match ip dscp af21 af22 ! Oracle may have been remarked to AF22 match access-group 103 ! Oracle uses TCP port 9000 ! class-map match-all REMARKED-DLSW+ match ip dscp af21 af22 ! DLSw+ may have been remarked to AF22 match protocol dlsw ! DLSw+ is identified by NBAR ! policy-map CE-INGRESS-EDGE class REMARKED-INTERACTIVE-VIDEO set ip dscp af41 ! Restores Interactive-Video marking to AF41 class REMARKED-CALL-SIGNALING set ip dscp af31 ! Restores Call-Signaling marking to AF31 class REMARKED-ORACLE set ip dscp 25 ! Restores Oracle marking to DSCP 25 class REMARKED-DLSW+ set ip dscp af21 ! Restores DLSw+ marking to AF21 ! ! interface serial 1/0 service-policy output CE-EGRESS-EDGE service-policy input CE-INGRESS-EDGE ! Marking restoration on ingress ! ! access-list 101 permit udp any any ! Identifies UDP traffic access-list 102 permit tcp any any ! Identifies TCP traffic access-list 103 permit tcp any eq 9000 any ! Identifies Oracle on TCP 9000 ! Verification commands: show policy show policy interface Three-Class Provider-Edge Model: CE Design In this model, the service provider offers three classes of service: Real-Time (strict priority, available in 5-percent increments), Critical Data (guaranteed bandwidth), and Best-Effort. The admission criterion for the Real-Time class is either DSCP EF or CS5; the admission criterion for Critical Data is DSCP CS6, AF31, or CS3. All other code points are re-marked to 0. Additionally, out-of-contract AF31 traffic can be marked down within the service provider’s MPLS VPN cloud to AF32. Enterprise QoS Solution Reference Network Design Guide 5-9
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:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Chapter 2 Campus QoS Design show ml
Page 115 and 116:
Chapter 2 Campus QoS Design Figure
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Chapter 2 Campus QoS Design show qo
Page 141 and 142:
Chapter 2 Campus QoS Design show qo
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Chapter 2 Campus QoS Design WS-X674
Page 155 and 156:
Chapter 2 Campus QoS Design Configu
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
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 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210: Chapter 3 WAN Aggregator QoS Design
Page 229 and 230: Version 3.3 Branch Router QoS Desig
Page 231 and 232: Chapter 4 Branch Router QoS Design
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: Chapter 5 MPLS VPN QoS Design Call-
Page 273 and 274: Chapter 5 MPLS VPN QoS Design Short
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 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 303 and 304: Chapter 6 IPSec VPN QoS Design Anti
Page 311 and 312:
Chapter 6 IPSec VPN QoS Design Vers
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?