BRKCRS-2501.Pdf

BRKCRS-2501.Pdf

BRKCRS-2501 Campus QoS Design - Simplified Roland Saville – Technical Leader Engineering Agenda • Campus QoS Design Considerations and Best Practices • Cisco Catalyst 2960-X / 3560-X / 3750-X QoS Design • Cisco Catalyst 9000 / 3850 / 3650 Series QoS Design • Cisco Catalyst 4500E QoS Design • Cisco Catalyst 6800 / 6500-E QoS Design • Meraki MS Series Switch QoS Design • Campus WLAN QoS Design Considerations and Best Practices • Cisco AireOS WLC AVC / QoS Design • Meraki MR Series AP QoS Design • What are we doing to make this simpler? • Summary and References BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 3 Cisco Webex Teams Questions? Use Cisco Webex Teams (formerly Cisco Spark) to chat with the speaker after the session How 1 Find this session in the Cisco Events Mobile App 2 Click “Join the Discussion” 3 Install Webex Teams or go directly to the team space 4 Enter messages/questions in the team space cs.co/ciscolivebot#BRKCRS-2501 BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 4 Campus QoS Design Considerations and Best Practices What Do You Consider First? BRKRST-2056: The QoS Paradigm Shift https://cisco.box.com/s/8izevlg4k6gaggh3cmrc16lugm6sdr8y https://www.ciscolive.com/online/connect/sessionDetail.ww?SESSION_ID=83633&backBtn=true BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 6 Start by Defining Your QoS Strategy Articulate Your Business Intent, Relevant Applications and End-to-End Strategy https://cisco.app.box.com/v/QoS-AAGs BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 7 The Case for Campus QoS • The primary role of QoS in campus networks is to manage packet loss • In campus networks, it takes only a few milliseconds of congestion to cause drops • Rich media applications are extremely sensitive to packet drops • Queuing policies at every node can prevent packet loss for real-time apps • The secondary role of QoS in campus networks is to condition traffic at the access edge, which can include any of the following: • Trust • Classify and Mark • Police BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 8 Why Is Video So Sensitive to Packet Loss? 1920 lines of Vertical Resolution (Widescreen Aspect Ratio is 16:9) 1080p60 1080 x 1920 lines = 2,073,600 pixels per frame x 24 bits of color per pixel x 60 frames per second = 2,985,984,000 bps or 3 Gbps Uncompressed! 1080 lines of Horizontal Resolution Cisco (H264/H.265) codecs transmit 3-5 Mbps per 1080p60 video stream which represents over 99.8% compression (~ 1000:1) Packet loss is proportionally magnified by compression ratios. Users can notice a single packet lost in 10,000 — Making HD Video One Hundred Times More Sensitive to Packet Loss than VoIP! BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 9 VoIP vs. HD Video—At the Packet Level Voice Packets Video Packets 1400 1400 Video Video Video Frame Frame Frame 1000 1000 Bytes 600 Audio 600 Samples 200 200 Time 20 msec 33 msec BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 10 Campus QoS Design Considerations How Long Can Queue-Buffers Accommodate Line-Rate Bursts? GE Linecard Example Begin dropping at 11 ms but overall utilization is only 1%! 140 Gbps Line Rate GE Linecard Example (WS-X6148) 120 ms 100 Total Per-Port Buffer: 5.4 MB 80 Per Per 60 Total Per-Queue Buffer*: 1.35 MB 40 20 Gbps Line Rate: 1 Gbps = 125 MB/s 0 or 125 KB/ms KBytes 10 50 90 450 570 690 810 170 210 250 290 330 370 410 490 530 610 650 730 770 850 890 930 970 130 Total Per-Queue Buffering Capacity: 10.8 ms ms *Assuming (4) equal-sized queues 1 second BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 11 Campus QoS Design Considerations How Long Can Queue-Buffers Accommodate Line-Rate Bursts? 10-GE Linecard Example Begin dropping at 9 ms but overall utilization is still only 1%! 1400 10 Gbps Line Rate 1200 10 GE Linecard Example (WS-X6908) ms 1000 Total Per-Port Buffer: 90 MB 800 Per Per 600 Total Per-Queue Buffer*: 11.25 MB 400 200 Gbps Line Rate: 10 Gbps = 1.25 GB/s 0 KBytes or 1250 KB/ms 10 50 90 210 410 610 810 130 170 250 290 330 370 450 490 530 570 650 690 730 770 850 890 930 970 Total Per-Queue Buffering Capacity: 9.0 ms ms *Assuming (8) equal-sized queues 1 second BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 12 Oversubscription in the Campus GE Link 10GE Link 40GE Link BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 13 Oversubscription in the Campus GE Link 10GE Link 40GE Link x 11 BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 14 Oversubscription in the Campus GE Link 10GE Link 40GE Link BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 15 Oversubscription in the Campus GE Link 10GE Link 40GE Link BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 16 Know Your Tools • Catalyst and Nexus switch hardware • Software and Syntax • Global Default QoS Settings • Trust States and Conditional Trust • Logical vs. Physical Interface QoS • Network Based Application Recognition (NBAR2) • Domain Name System—Authoritative Source (DNS-AS) • Ingress and Egress Queuing Models BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 17 Economy Hardware Varies Utility Performance BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 18 Software and Syntax Variations • Catalyst 2960-X/3560-X/3750-X are the last platforms to use Multilayer Switch QoS (MLS QoS) • QoS is disabled by default and must be globally enabled with the mls qos command • Once enabled, all ports are set to an untrusted port-state • Catalyst 9000, Catalyst 3650/3850, and Catalyst 4500E use IOS Modular QoS Command Line Interface (MQC) • QoS is enabled by default • All ports trust at layer 2 and layer 3 by default • Catalyst 6500-E/6800 (Sup6T & Sup2T) use Cisco Common Classification Policy Language (C3PL) QoS • QoS is enabled by default • All ports trust at layer 2 and layer 3 by default • C3PL presents queuing policies similar to MQC, but as a defined “type” of policy • Nexus 7000/7700 use NX-OS QoS • QoS is enabled by default • All ports trust at layer 2 and layer 3 by default • NX-OS presents queuing policies similar to MQC, but as a defined “type” and with default class-map names BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 19 Trust Boundary Trust Boundaries Untrusted / User-Administered Devices no mls qos trust The trust boundary is the edge where • Layer 2 (CoS / UP) and/or • Layer 3 (DSCP) Trust Boundary QoS markings are accepted or rejected Trusted Centrally-Administered Devices mls qos trust dscp Trust Boundary Centrally-Administered & Conditionally-Trusted Devices mls qos trust device • cisco-phone • cts • ip-camera • media-player BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 20 Conditional Trust Trust Boundary Extension to Cisco Devices If a Cisco IP Phone is detected then the trust boundary extends to the IP Phone Access Switch CoS-to-DSCP Mapping Table CoS 7 DSCP CS7 (56) The IP Phone sets CoS for Voice and CoS 6 DSCP CS6 (48) Signaling and resets all else to 0 IP Phone CoS 5 DSCP EF (46)* CoS Mapping Table CoS 4 DSCP CS4 (32) The access switch maps CoS-to-DSCP CoS 6-7 CoS 0 CoS 3 DSCP CS3 (24) Voice CoS 5 CoS 2 DSCP CS2 (16) Signaling CoS 3 CoS 1 DSCP CS1 (8) CoS 0-4 CoS 0 CoS 0 DSCP DF (0) * Non-Default Mapping Trust Boundary BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 21 Policy Enforcement Points (PEPs) • The Policy Enforcement Point (PEP) is the edge where classification and marking policies are enforced • The PEP may or may not be the same as the trust boundary • Multiple PEPs may exist for different types of network devices • e.g. switch PEP vs. router PEP Note: For the sake of simplification, in this deck PEP will refer to Trust Boundary classification and marking policy enforcement points (only) Switch Router and will not include other policy enforcement points (e.g. queuing). PEP PEP BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 22 Per-Port QoS vs. Per-VLAN QoS Per-Port QoS Per-VLAN QoS Policy map is applied to the logical VLAN interface VLAN Interfaces VLAN Interfaces Vlan10 Vlan20 Vlan10 Vlan20 Physical Ports Physical Ports Policy map is applied to the interface gig 1/1-48 physical switch port mls qos vlan-based interface gig 1/1-48 interface Vlan 10 service-policy input MARKING service-policy input MARKING BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 23 NBAR in Hardware—Yesterday • Cisco Catalyst 6500 Sup32 Programmable Intelligent Services Accelerator (PISA)—Jan 2007 • Supported 90+ protocols • Maximum Throughput: ~2 Gbps BRKCRS-2501 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 24 NBAR2 in Hardware—Today • UADP-based platforms: • Catalyst 3650 • Catalyst 3850 • Catalyst 9000 Series (UADP 2.0 or 3.0) • Supported 1400+ protocols 1400% increase • Maximum Throughput (Catalyst 3850 / 3650): • ~500 connections per second at less than 50% CPU • Up to 5,000 bi-directional flows (24 access ports) • Up to 10,000 bi-directional flows (48 access ports) • Maximum Throughput (Catalyst 9000): • ~2000 connections per second at less than 50% CPU • Up to 10,000 bi-directional flows (24 access ports) • Up to 20,000 bi-directional flows (48 access ports) BRKCRS-2501 © 2019 Cisco and/or its affiliates.

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    277 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us