Alright... I have QoS Deployed and working on my LAN, ingress marking everything appropriately at the edge (3750 stacks), and The core is trusting ingress traffic from the edge. What I have not yet figured out is how to get my traffic re-marked to match my WAN QoS policy. Effectively I want to restrict Marking of Video Traffic to a specific Video Conference system or group of Video Conference Systems (either based on MAC/Current Marking, or IP/Port matching so that only specific systems get QoS on the WAN (basically if they purchase QoS for a specific Unit).
I have 2 site models:
Cisco 6509 Core Switches, with Sup720's, with WS-X6748-SFP and WS-X6748-GE-TX blades running Modular IOS. Handing off to the Service Providers CE Router on a .1q trunk from the GE-TX blade.
Cisco 3750 switch stack, running IOS, and handing off L3 routed interface to the Service Providers CE Router.
PFC QoS supports the output keyword only with a PFC3 and only on Layer 3 interfaces (either LAN ports configured as Layer 3 interfaces or VLAN interfaces). With a PFC3, you can attach both an input and an output policy map to a Layer 3 interface.
You may want to open a service request at this point to see what else can be done.
There is a link now from the community to open a TAC case.
Inviting all network professionals in operations! We'd like to understand what would be valuable for you in a mobile application. Your response will help Cisco improve a product feature that could benefit you. Thanks!
Click here to take the sur...
Cisco’s software-defined wide area network (SD-WAN) solution allows user to quickly and seamlessly establish an overlay fabric to connect an enterprise’s data centers, branch and campus locations, as well as colocation facilities in order to imp...
1. Log into CLI of DNAC:
ssh maglev@< DNAC appliance IP> -p 2222
2. Run this curl command to get token to get member id:
curl -X POST -u admin:<admin user password> -H -V https://<CLUSTER-IP>/api/system/v1/identitymgmt/token
Enterprise Switching Business Unit is glad to announce Beta release 16.12.2 for all Catalyst 9200/9300/9400/9500/9600 and Catalyst 3650/3850 Platforms. This release is made available to allow users to test, evaluate and share fee...
Purpose of the document
This document describes the general recommendations or best practices when designing and deploying the Cisco SD-Access technology. The document assumes that the reader has a general overview of Cisco's SD-Access for Distributed C...