07-30-2014 12:56 PM - edited 03-07-2019 08:13 PM
Hello -
I am configuring an interface on a 3650 switch for a device that is being moved from a 3550 switch. I found that some commands that were configured on the 3550 interface are not available on the 3650:
mls qos trust device cisco-phone
mls qos trust dscp
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
From 3550 interface config:
switchport access vlan 100
switchport trunk encapsulation dot1q
switchport mode access
duplex full
speed 100
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
mls qos trust device cisco-phone
mls qos trust dscp
auto qos voip cisco-phone
spanning-tree portfast
spanning-tree bpduguard enable
From 3650 interface config:
switchport access vlan 100
switchport mode access
speed 100
duplex full
trust device cisco-phone
auto qos voip cisco-phone
spanning-tree portfast
spanning-tree bpduguard enable
service-policy input AutoQos-4.0-CiscoPhone-Input-Policy
service-policy output AutoQos-4.0-Output-Policy
MLS commands do not appear to be available on the 3650 switch. Am I losing functionally on the 3650 or is the a way to enable the use of these commands?
Any advice on this issue is appreciated.
Solved! Go to Solution.
07-30-2014 05:22 PM
Hi,
You will not find the same commands on the 3650 since this is IOS-XE software and it uses the MQC qos model therefore it works different.
This means that instead of using certain global configurations, auto-QoS applied to any interface on a switch configures several global class maps and policy maps, reason why you see an input/output policy map on the interface configuration. You should not be losing the functionality of the auto qos.
Here is a link that covers the auto qos on 3650 switches:
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3650/saoftware/release/3se/qos/configuration_guide/b_qos_3se_3650_cg/b_qos_3se_3650_cg_chapter_011.html
Hope this helps.
07-30-2014 05:22 PM
Hi,
You will not find the same commands on the 3650 since this is IOS-XE software and it uses the MQC qos model therefore it works different.
This means that instead of using certain global configurations, auto-QoS applied to any interface on a switch configures several global class maps and policy maps, reason why you see an input/output policy map on the interface configuration. You should not be losing the functionality of the auto qos.
Here is a link that covers the auto qos on 3650 switches:
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3650/saoftware/release/3se/qos/configuration_guide/b_qos_3se_3650_cg/b_qos_3se_3650_cg_chapter_011.html
Hope this helps.
09-27-2017 05:08 AM
09-27-2017 05:28 AM
09-27-2017 05:30 AM
Awesome! Thanks!
09-27-2017 05:33 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide