Cisco Catalyst 3650 Series, Command Reference Manual

Page: 652 / 1108

The device applies the auto-QoS-generated commands as if the commands were entered from the
command-line interface (CLI). An existing user configuration can cause the application of the generated
commands to fail or to be overridden by the generated commands. These actions occur without warning.
If all the generated commands are successfully applied, any user-entered configuration that was not
overridden remains in the running configuration. Any user-entered configuration that was overridden can
be retrieved by reloading the device without saving the current configuration to memory. If the generated
commands fail to be applied, the previous running configuration is restored. Note
If this is the first port on which you have enabled auto-QoS, the auto-QoS-generated global configuration
commands are executed followed by the interface configuration commands. If you enable auto-QoS on another
port, only the auto-QoS-generated interface configuration commands for that port are executed.
When you enter the auto qos voip cisco-phone interface configuration command on a port at the edge of the
network that is connected to a Cisco IP phone, the device enables the trusted boundary feature. The device
uses the Cisco Discovery Protocol (CDP) to detect the presence of a Cisco IP phone. When a Cisco IP phone
is detected, the ingress classification on the port is set to trust the QoS label received in the packet. The device
also uses policing to determine whether a packet is in or out of profile and to specify the action on the packet.
If the packet does not have a DSCP value of 24, 26, or 46 or is out of profile, the device changes the DSCP
value to 0. When a Cisco IP phone is absent, the ingress classification is set to not trust the QoS label in the
packet. The policing is applied to those traffic matching the policy-map classification before the device enables
the trust boundary feature.
•
•
When you enter the auto qos voip cisco-softphone interface configuration command on a port at the
edge of the network that is connected to a device running the Cisco SoftPhone, the device uses policing
to decide whether a packet is in or out of profile and to specify the action on the packet. If the packet
does not have a DSCP value of 24, 26, or 46 or is out of profile, the device changes the DSCP value to
0.
• When you enter the
auto qos voip trust
interface configuration command on a port connected to the
network interior, the device trusts the CoS value for nonrouted ports or the DSCP value for routed ports
in ingress packets (the assumption is that traffic has already been classified by other edge devices).
You can enable auto-QoS on static, dynamic-access, and voice VLAN access, and trunk ports. When enabling
auto-QoS with a Cisco IP phone on a routed port, you must assign a static IP address to the IP phone.
When a device running Cisco SoftPhone is connected to a device or routed port, the device supports only
one Cisco SoftPhone application per port.
Note
After auto-QoS is enabled, do not modify a policy map or aggregate policer that includes AutoQoS in its name.
If you need to modify the policy map or aggregate policer, make a copy of it, and change the copied policy
map or policer. To use the new policy map instead of the generated one, remove the generated policy map
from the interface, and apply the new policy map.
To display the QoS configuration that is automatically generated when auto-QoS is enabled, enable debugging
before you enable auto-QoS. Use the
debug auto qos
privileged EXEC command to enable auto-QoS
debugging.
The following policy maps and class maps are created and applied when running the auto qos voip trust
command:
Command Reference, Cisco IOS XE Everest 16.5.1a (Catalyst 3650 Switches)
626
auto qos voip