Symptom
While working with customer we have observed the issue on ASR 1k XE release 17.3.1, when the customer was applying QoS policies to the virtual-access interfaces we noticed that the router wasn’t able to activate the output HQOS Policy for the V6 VA interface. The Policy remained in suspended mode. We tried to set bandwidth and tunnel bandwidth commands under the VA interfaces by modifying the local AAA attributes, but we experienced the same issue. we also tried to deactivate the V4 tunnel and keep the V6 tunnel running, the same issue.
You can find the output QoS policies below as policy in suspended mode.
#sh derived-config interface virtual-access 2
Load for five secs: 1%/0%; one minute: 0%; five minutes: 0%
Time source is NTP, *11:37:21.293 MET Wed Feb 17 2021
Building configuration...
Derived configuration : 467 bytes
!
interface Virtual-Access2
description Auto Template for IPX Customers
vrf forwarding IPX-ALL
ipv6 unnumbered Loopback2
tunnel source
tunnel mode ipsec ipv6
tunnel destination
tunnel path-mtu-discovery
tunnel vrf RED
tunnel protection ipsec profile ipx-ikev2
no tunnel protection ipsec initiate
service-policy input IPSEC_IN_CM_POLICING_PARENT_40M
service-policy output IPSEC_OUT_SHAPING_PARENT_40M
end
#sh policy-map interface Virtual-Access2 o
Load for five secs: 0%/0%; one minute: 0%; five minutes: 0%
Time source is NTP, *11:38:23.839 MET Wed Feb 17 2021
Virtual-Access2
Service-policy output: IPSEC_OUT_SHAPING_PARENT_40M
Service policy IPSEC_OUT_SHAPING_PARENT_40M is in suspended mode
Conditions
While applying QoS policies to the virtual-access interfaces we noticed that the router wasn’t able to activate the output HQOS Policy for the V6 VA interface. The Policy remained in suspended mode.
Workaround
Issue is fixed in upcoming release 17.3.5
