Solved: QoS for UCM on Supervisor 2T

Colin Higgins · ‎10-08-2013

I have a basic QoS setup on my 6500 with a Supervisor 2T

I am using auto qos voip cisco-phone on the ports with phones attached

But what do I do for the ports where my call manager (UCM) is attached

I have templates and guides for the older architectures (Sup32, 720, etc.), but I have no idea what to do on the Supervisor 2T

Does anyone have an example of a basic QoS setup for those ports?

brmeade · ‎10-08-2013

Just do auto qos voip trust on those ports.

View solution in original post

islam.kamal · ‎10-10-2013

Hi

That means trust DSCP enable by default under ports . This is ok nowadays , as all environement has many traffic for voice , data and video. Any way , i think you have to find the below table . If you need go to post your question also with infrastructure - LAN routing and switching on CSC , i think people their many have experience for your issue.

Table 8. Summary of Command Migration for Cat6500 Specific Global CLI

PFC3 Command	Sta-tus	PFC4 Migration NVGEN and Action	Comments on PFC4 Behavior
mls qos	P	auto qos default Used in mls qos trustmigration actions as indicator of existing PFC3 configuration	Auto-configure default queueing on ports without queueing policy. No direct effect on Earl policing/marking. Migration actions triggered if mls qosis seen on bootup or on configuration copy.
no mls qos	I	Ignored	No effect in PFC4 platform
mls qos queueing-only	R	platform qos queueing-only	Queueing behavior identical to auto qos default. Policing/marking and DSCP/CoS rewrite is disabled.
no mls qos rewrite ip dscp	P	no platform qos rewrite ip dscp	Same behavior as in PFC3. Not necessary: PFC4 rewrite control is per-class
mls qos marking ignore port-trust	I	Used as indicator that PFC3 port trust commands can be ignored	Port trust ignored in PFC4 marking, by default
mls qos marking statistics	R	platform qos marking statistics	Same behavior as in PFC3
mls qos police serial	I	Ignored	Serial mode is always on in PFC4
mls qos police redirected	I	Ignored	Ingress policing of redirected packets is always enabled Egress policing of packets to RP is always disabled, except for CPP Egress policing of packets, redirected to service cards, is controlled by a policy on the respective egress VLAN
mls qos map	R	table-map	Same behavior as in PFC3. Certain dscp map names are auto-converted to discard-class map names
mls qos aggregate-policer	R	platform qos aggregate-policer	Same behavior as in PFC3
mls qos protocol	R	platform qos protocol	Same behavior as in PFC3
mls qos statistics-export	R	platform qos statistics-export	Same behavior as in PFC3
mac packet-classify use vlan	I	N/A	VLAN field is always enabled in PFC4 MAC ACLs
mls qos gre input uniform-mode (ST2)	I	N/A	Uniform mode is default and is controlled by C3PL per ingress policy class
mls mpls input uniform-mode (ST2)	I	N/A	Uniform mode is default and is controlled by C3PL per ingress policy class

Table 9. Summary of Command Migration for Cat6k Specific Interface CLI

PFC3 Command	Sta-tus	PFC4 Migration NVGEN and Action	Comments on PFC4 Behavior
mls qos trust cos	R	platform qos trust cos	Initial ingress discard-class mapped from COS. Does not rewrite packet DSCP. PFC4 Differences: In port-based mode, port trust cos is ignored if there is a port (ingress) policy In VLAN-based mode, port trust cos is ignored in both default and VLAN policy case
mls qos trust dscp	I	N/A	Default behavior in PFC4 and C3PL
mls qos trust precedence	I	N/A	Handling is the same as mls qos trust dscp. Low 3 bits of incoming DSCP are not zeroed
no mls qos trust	R	platform qos trust none remark	Converted to trust none if mls qos present, otherwise, ignored. Ignored in VLAN-based mode
mls qos trust extend	R	platform qos trust extend	Same behavior as in PFC3
mls qos trust device	R	platform qos trust device	Same behavior as in PFC3
mls qos mpls trust experimental	R	platform qos mpls trust experimental	Same behavior as in PFC3
mls qos vlan-based	R	platform qos vlan-based	Same behavior as in PFC3
mls qos dscp-mutation	R	platform qos dscp-mutation	Same behavior as in PFC3
mls qos exp-mutation	R	platform qos exp-mutation	Same behavior as in PFC3
mls qos statistics-export	R	platform qos statistics-export	Same behavior as in PFC3
mls qos bridged	I	N/A	Auto-enabled/disabled internally per NetFlow profile, depending on the presence of microflow policing
mac packet-classify	R	mac packet-classify input	Equivalent to mac packet-classify input
mls qos loopback	R	platform qos loopback	Same behavior as in PFC3
mls qos queueing mode	R	platform qos queueing mode	Same behavior as in PFC3. Not supported in C3 LCs
mls qos cos	R	platform qos cos	Same behavior as in PFC3
wrr-queue	R	wrr-queue	Same behavior as in PFC3. Not supported in C3 LCs
rcv-queue	R	rcv-queue	Same behavior as in PFC3. Not supported in C3 LCs
pri-queue	R	pri-queue	Same behavior as in PFC3. Not supported in C3 LCs
mls qos channel-consistency	R	platform qos channel consistency	Enabled by auto qos default. Future: member ports must have the same ingress and egress queueing policy.

Table 10. Summary of Migration for Cat6K Specific Policy Map Commands

PFC3 Command	Sta-tus	PFC4 Migration NVGEN and Action	Comments on PFC4 behavior
trust dscp	R	trust dscp	Default behavior in PFC4 and C3PL
trust precedence	R	trust precedence	Handling is the same as trust dscp. Low 3 bits of incoming DSCP are not zeroed
trust cos	R	trust cos	PFC4 Differences: The incoming 802.1q CoS is always used unless port CoS override configured. Warning to user to use set dscp cos or set-dscp-cos-transmit in police conform-action.
no trust	I	N/A	Packet QoS is preserved by default
police {exceed\| violate} policed-dscp	R	police... {exceed\| violate} policed-dscp	Retained as part of C3PL syntax
police flow	R	police flow	Retained as part of C3PL syntax
police aggregate	R	police aggregate	Retained as part of C3PL syntax

Thank you

please rate all useful information

View solution in original post

brmeade · ‎10-08-2013

Just do auto qos voip trust on those ports.

Colin Higgins · ‎10-09-2013

Ah ok lol

If the UCM server is on a port-channel, do I do auto qos voip trust on the channel interface or do I have to do it on each individual interface/

islam.kamal · ‎10-09-2013

Hi

The QOS should be enabled under the physical port not port channel. You have to to enable it to your physical ports.

Thank you

please rate all useful information

Colin Higgins · ‎10-09-2013

Apparently,

auto qos voip trust

is not supported on port-channels

Someone said something about taking the config that would normally be applied and doing it manually

would that be

priority-queue queue-limit 5

wrr-queue queue-limit 65 15 15

wrr-queue random-detect min-threshold 1 70 100 100 100 100 100 100 100

wrr-queue random-detect min-threshold 2 70 100 100 100 100 100 100 100

wrr-queue random-detect min-threshold 3 40 40 50 50 60 60 70 70

wrr-queue random-detect max-threshold 1 100 100 100 100 100 100 100 100

wrr-queue random-detect max-threshold 2 100 100 100 100 100 100 100 100

wrr-queue random-detect max-threshold 3 70 70 80 80 90 90 100 100

wrr-queue cos-map 2 1 1 2

wrr-queue cos-map 3 5 3 4

wrr-queue cos-map 3 7 6 7

?

islam.kamal · ‎10-09-2013

Hi

As i mentioned above the auto qos voip trust , should be applied under physical ports not inder port channel.

Thank you

please rate all useful information

islam.kamal · ‎10-09-2013

Hi

1- priority-queue, mls qos trust and auto qos voip trust commands apply under physical ports , for Port channel just configuration for (switchport mode tunk , etc).

Thank you

please rate all useful information

Colin Higgins · ‎10-09-2013

I won't accept the auto qos voip option on any of the physical ports if those ports are members of a port-channel

islam.kamal · ‎10-09-2013

HI

i am sure that the above will meet you case your case , but if your have a scinario as QOS and mls dscp & mls cos. In this case under the portchannel you can apply mls qos trust dscp trust . If i have a traffic for example MGCP and you do a QOS with access lists, class maps , pilcy map then you have to apply. In this case you can use your port channel to trust th incoming traffic. This QOS portchannel only supportd for (ASR , GSR, 6500,N7K,etc).

Thank you

please rate all useful information

islam.kamal · ‎10-09-2013

Hi

my answer about the command which you mentioned above. Please tell me the port chanel will be as L3 , trunk or what ?.After that i can help you to do a configuration which will be ok.

Thank you

please rate all useful information

Colin Higgins · ‎10-09-2013

The trunk uses LACP for port-aggregation and the port-channel interface has an IP assigned.

6 interfaces are in the group

config:

interface Port-channel71

switchport

switchport trunk allowed vlan 97,98

switchport mode trunk

switchport nonegotiate

I have auto qos assigned to phone ports and voice router ports: the environment is pretty basic--it is a remote office that serves as a call center, so there are no competing video streams, heavy DB traffic etc.

islam.kamal · ‎10-09-2013

Hi

for your case under portchannel , please try the below and dont do any thing on the pysical members

mls qos

mls qos map cos-dscp 0 8 16 24 34 46 48 56

Switch(config-if)#wrr-queue bandwidth 30 70

Switch(config-if)#wrr-queue threshold 1 40 100

Switch(config-if)#wrr-queue threshold 2 80 100

Switch(config-if)#wrr-queue cos-map 1 1 1

Switch(config-if)#wrr-queue cos-map 1 2 0

Switch(config-if)#wrr-queue cos-map 2 1 2 3 4 6 7

Switch(config-if)#wrr-queue cos-map 2 2 5

Switch(config-if)#mls qos trust dscp

Thank yo

please rate all useful information

Colin Higgins · ‎10-10-2013

Will that configuration work for the

WS-X6148E-GE-45AT

line cards?

(thanks for your help by the way!)

islam.kamal · ‎10-10-2013

Hi

As a sample configuration it should work so fine , did you test ?. Please test and share with me.Please find also the below link

http://www.dslreports.com/faq/13324

Thank you

please rate all useful information

Colin Higgins · ‎10-10-2013

won't let me do this on the port-channel interface (po70 or po71)

no wrr-queue or mls options

It does accept the wrr-queue options under the physical interface, but will not take any mls related commands (so I am not sure how to specify trust).

I think this is because of the new Supervisor 2T -everything appears to be different