Simplifying QoS across your Cisco Digital Network Architecture Nectar Evolution Simplifying QoS across your Cisco Digital Network Architecture Steven Purcell

What We Are Here To Talk About Unified Communications Cisco Powered Network Quality of Service This slide builds from left to right. This slide will help to build the foundation of the story you are about to tell. Why are we here today and what are we talking about? I have said, “We are going to talk about, Unified Communications, your Cisco Powered Network, and QoS.”

Multi-Vendor Platforms QoS/QoE Complexity Collaboration QoE must be end-to-end. Designs need to be comprehensive and cohesive across: Multi-Vendor Platforms Media Location We are showing on this slide that QoS is complex. In order to properly apply QoS in an environment you have to properly account for these different factors. Mulit-Vendor platforms. There are a lot of different types of technology platforms that need different levels of QoS. Multiple modalities / media types All of this complexity is enhanced by being spread across large geographic regions.

“It takes [us] 4 months and $1M to push a QoS change… I view the administrator as being a business analyst via a central station without needing to have any understanding of QoS models and low level device attributes.” —Wall Street Financial Customer Example of QoS costs to the business.

“It took us 3 months to deploy a 2 line ACL change across 10K devices, which slowed down onboarding of our Jabber application.” —Enterprise Network Architect Example of QoS costs to the business.

Healthcare case study - QOS change cycle Problems caused by this cycle can be: Policies can take a long time to implement. Due to the complexity some policies never get applied. Companies may choose to ignore them due to the overwhelming complexity of fixing them. They are never done. There is constant tweaking of policies that needs to be done, there is a constant need to add and delete policies, and there are just too any devices to keep up with to get anywhere close to optimizing policies.

Announcing Nectar Evolution Dynamic Policy Engine

Cisco Digital Network Architecture (DNA) brings controller-based automation, rich contextual analytics, network functions virtualization (NFV), and limitless scalability of the cloud to Cisco powered networks. The APIC-EM delivers SDN to the Enterprise to the WAN, Campus and Access networks. APIC-EM provides centralized automation of policy- based application profiles with is EasyQoS functionality. Cisco Integration

APIC-EM EasyQoS Solution Applications can interact with APIC-EM via Northbound APIs, informing the network of application-specific and dynamic QoS requirements Network Operators express high-level business-intent to APIC-EM EasyQoS EM Southbound APIs translate business-intent to platform-specific configurations Wireless AP Trust Boundary PEP 4Q (WMM) This slide is showing how application’s like Nectar evolution interface with APIC-EM. This slide helps show that it’s not Nectar Evolution that applies QoS policies and interfaces with the network, it’s Cisco’s own application that does this. Catalyst 3650 Trust Boundary PEP 2P6Q3T WLC PEP Wireless AP Trust Boundary PEP 4Q (WMM) ASR/ISRs MQC Catalyst 2960-X Trust Boundary PEP 1P3Q3T Catalyst 4500 1P7Q1T Catalyst 6500 1P3Q4T 1P7Q4T 2P6Q4T … Nexus 7700 F3: 1P7Q1T

Cisco APIC-EM Integration Collaboration Devices Nectar Evolution APIC-EM Network Devices

Genomes of Evolution with APIC-EM for Cisco DNA Verification Quality of Service Security Unified Communications Application UC Registered User / Device Verification Pre-Defined Audio / Video Policies Trust Audio / Video DSCP Markings From Verified UC Devices

Primary First Use Case - Nectar Evolution Wired Use Case Collaboration Devices Nectar Evolution APIC-EM Network Devices Unified Communications Registrations This is an expanded version of slide 11 that focuses on a wired network example. How to talk to this slide: The collaboration device registers to call control. This can be CUCM or Skype for Business front end. There is a Skype and Jabber client shown here. Nectar Evolution is aware of registration and deregistration of devices because we talk to call control. Evolution makes APIC-EM aware that a UC device has registered or deregistered from the network. APIC-EM will apply the appropriate UC QoS policy to the wired network device the device is attached to. Dynamic Policy Engine

Nectar Evolution Wireless Use Case* User Wi-Fi Registration Nectar Evolution APIC-EM Single AP QoS Policy Unified Communications Registrations **APIC-EM will not have support for wireless until APIC-EM 2.0 hopefully to be released around the summer of 2017. This is an expanded version of slide 11 that focuses on a wireless network example. This use case is strong since QoS is fairly new to wireless networks. It will be easier to get customers to agree to let APIC-EM take over QoS on a wireless network where there is no QoS today. How to talk to this slide: The collaboration device registers to call control. This can be CUCM or Skype for Business front end. There is a Skype and Jabber client shown here. Nectar Evolution is aware of registration and deregistration of devices because we talk to call control. Evolution makes APIC-EM aware that a UC device has registered or deregistered from the network. APIC-EM will apply the appropriate UC QoS policy to the wireless network device the device is attached to. Dynamic Policy Engine * Coming Q4 2017 with APIC-EM 2.0

Supported infrastructure – Evolution v1.0 Unified Communications Cisco CUCM 9.x CUCM 10.x CUCM 11.x Microsoft Lync 2013 Skype for Business LAN WAN Supported Switches Catalyst 3560CG Series Catalyst 3560-X Series Catalyst 3750-X Series (Stack) Catalyst 2960-S Series (Stack) Catalyst 2960-X Series Catalyst 4500(Sup7E) Series Catalyst 4500E(Sup8E) Series Catalyst 3650 Series Catalyst 3850 Series (Stack) Catalyst 6500 (Sup2T) Series Catalyst 6880-X Series Supported Routers Cisco ISR G2 Cisco ISR 4451 Cisco ASR 1000 Series Cisco Network Example APIC-EM Supported Devices This list updates frequently, please see this link for an updated list: http://www.cisco.com/c/en/us/td/docs/cloud- systems-management/application-policy- infrastructure-controller-enterprise-module/1-4- x/easyqos/supported- platforms/b_EasyQoS_Supported_Devices_1_4_0_ x.html?#_=_ Hide for press