Auto QoS
Enabling AutoQos failed at interface
Symptom: An Error message will be thrown when auto-qos is enabled at the interface level.
Problem
description: Auto-qos can be enabled for an interface by executing “enable-auto-qos”
command at interface qos level. Enabling auto-qos will create pre-defined classes on the
interface and enable Policing or CBQ functionality on the interface. There can be two reasons
for auto-qos to fail on an interface: 1. Auto-qos is in manual state 2. Interface doesn’t have
enough buffers
Case –1: Auto-qos will be applied in inbound direction for ethernet interfaces and outbound
direction for bundle interfaces. So for applying auto-qos for an interface it should not have any
manual configuration in the specific direction. For bundle interfaces: 1. No policy-map should
be attached to outbound direction 2. No QoS features (policing, CBQ, monitoring) should be
enabled on the outbound direction of the interface. For Ethernet interfaces: 1. No policy-map
should be attached to inbound direction 2. No QoS features (policing, monitoring) should be
enabled on the inbound direction of the interface If the above conditions are not met then
applying auto-qos will fail for that interface.
Case – 2: For applying auto-qos on bundle interfaces, a minimum of 28 class buffers is needed.
Buffers are calculated based on the interface bandwidth. So if the interface doesn’t have
enough buffers then auto-qos will fail.
Prerequisite: Interface should be successfully created.
Troubleshooting tips:
• Remove
all the manual configurations in the specified direction (outbound for bundle and
inbound for ethernet). Use “show qos chassis [interface-type] [interface-
name]” to verify the QoS configurations for that interface.
• Make sure that enough buffers are available in the interface. Use “show qos chassis
[interface-type] [interface-name]” to verify the buffers available for that
interface. If it is a bundle interface try adding more links to the bundle.
Enable or disable at global level does not change the auto-qos status at interface
level
Symptom: • Interface auto-qos status will be shown as disabled in show qos chassis
[interface-type] [interface-name].
Problem description: Auto-qos can be enabled for all interfaces by executing “enable-auto-
qos” command at global qos level. Enabling auto-qos will create predefined classes on all
applicable interfaces and enable Policing or CBQ functionality on the interfaces. There can be
Troubleshooting Quality of Service
256 Troubleshooting August 2013
Comments? infodev@avaya.com
To Next Page
Loading...
