Preview Tool

Cisco Bug: CSCvt56401 - aclqos crash when configure new QOS group in case of system qos already apply

Last Modified

Jun 17, 2020

Products (1)

  • Cisco Nexus 3000 Series Switches

Known Affected Releases

7.0(3)I7(7) 7.0(3)I7(8)

Description (partial)

device rebooted and following logs could see
2010 Feb 19 10:09:37 switch %SYSMGR-SLOT1-2-SERVICE_CRASHED: Service "aclqos" (PID 3201) hasn't caught signal 11 (core will be saved).
2010 Feb 19 10:09:38 switch %SYSMGR-SLOT1-2-SERVICE_CRASHED: Service "aclqos" (PID 3915) hasn't caught signal 11 (core will be saved).
2010 Feb 19 10:09:38 switch %SYSMGR-SLOT1-2-HAP_FAILURE_SUP_RESET: Service "aclqos" in vdc 1 has had a hap failure
2010 Feb 19 10:09:38 switch %SYSMGR-SLOT1-2-LAST_CORE_BASIC_TRACE: fsm_action_become_offline: PID 17099 with message Could not turn off console logging on vdc 1 error: mts req-response with syslogd in vdc 1 failed (0xFFFFFFFF)  .

1) already apply following QOS in system qos.
policy-map type qos SET-QOS-Group
class type qos Protocol_APPLICATION
set qos-group 1
class type qos DB_APPLICATION
set qos-group 2
class type qos JY_APPLICATION
set qos-group 3
class type qos Data_SYNC_APPLICATION
set qos-group 4
class type qos MGMT_APPLICATION
set qos-group 5
system qos
service-policy type qos input SET-QOS-Group

2) Then add a new group in this qos, after configure that, they find this QOS crash. 
N3K-2(config-pmap-c-qos)# class type qos Antivirus_APPLICATION
Bug details contain sensitive information and therefore require a 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.