Guest

Preview Tool

Cisco Bug: CSCun21177 - asr 901 cos-based ingress policy not working consistently

Last Modified

Mar 29, 2019

Products (16)

  • Cisco ASR 901 Series Aggregation Services Routers
  • Cisco ASR 901-6CZ-F-D Router
  • Cisco ME 3600X-24TS-M Switch
  • Cisco ASR 901-4C-FT-D Router
  • Cisco ASR 901S-4SG-F-D Router
  • Cisco ASR 901S-2SG-F-D Router
  • Cisco ASR 901-6CZ-F-A Router
  • Cisco ASR 901-6CZ-FT-A Router
  • Cisco ASR 901-12C-FT-D Router
  • Cisco ASR 901S-3SG-F-D Router
View all products in Bug Search Tool Login Required

Known Affected Releases

15.4(1)S

Description (partial)

Symptom:
CoS-based ingress QoS policy stopped working after router reload.

The ingress policy configured as:

policy-map trust-ingress-cos
 class class-default
  set qos-group cos

And applied to input port as follows:

interface GigabitEthernet0/4
 service-policy input trust-ingress-cos
 ...

The above ingress policy worked fine initially - input data with different L2 cos values ended up in different egress QoS queues.

Conditions:
After router reload, all traffic ended in egress default queue.
Verified ingress policy remained configured at ingress port after reload.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.