Description

This article will explain the meaning, possible triggers, impact, and ways to mitigate the following syslog messages: 
  • BRCM_COS_HALP(brcm_cos_bind_fixed_classifier_ifl_pvt:3951): Bind of non-existent fixed classifier with pri (0)  on IFL (561)
  • BRCM_COS_HALP(brcm_cos_classifier_type_bind_svp:1238): Classifier bind to IFL 561 failed

This is applicable for all QFX and EX platforms
 

Symptoms

The below syslog messages might be seen on the device when a configuration change related to the fixed classifier is made. For example, when a fixed classifier is changed from one classifier to another or when the fixed classifier is applied to multiple interfaces and then removed from some of the interfaces.
 

%PFE-3: fpc0 BRCM_COS_HALP(brcm_cos_bind_fixed_classifier_ifl_pvt:3951): Bind of non-existent fixed classifier with pri (0)  on IFL (556)

%PFE-3: fpc0 BRCM_COS_HALP(brcm_cos_classifier_type_bind_svp:1238): Classifier bind to IFL 556 failed

%PFE-3: fpc0 BRCM_COS_HALP(brcm_cos_fixed_classifier_delete:309):  Could not find qos map id  for fixed classifier pri : 0

%PFE-3: fpc0 BRCM_COS_HALP(brcm_cos_bind_fixed_classifier_ifl_pvt:3951): Bind of non-existent fixed classifier with pri (0)  on IFL (557)

%PFE-3: fpc0 BRCM_COS_HALP(brcm_cos_classifier_type_bind_svp:1238): Classifier bind to IFL 557 failed

%PFE-3: fpc0 BRCM_COS_HALP(brcm_cos_fixed_classifier_delete:309):  Could not find qos map id  for fixed classifier pri : 0

Solution

Decoding the syslog message “Bind of the non-existent fixed classifier with pri (0)  on IFL (556)”.
 

556 is the interface index which can be identified using the command “show interfaces extensive”

  user@Device> ...0 extensive | match "Logical interface"  

  Logical interface et-0/0/0.2000 (Index 565) (SNMP ifIndex 582) (HW Token 4095)
 

The syslog message indicates a non-existent fixed classifier was being applied to the interface and it failed.
 

Scenarios that may cause the above issue:

  1. The same forwarding class is applied to two different interfaces at the same time, and then the forwarding class for one of the interfaces is changed and committed to a different value.
  2. Forwarding class on all interfaces is changed from one value to another.


The above scenarios can lead to the generation of these syslogs. In the hardware, all fixed classifiers will have the same ID and when the above configuration changes are committed, this ID gets assigned to another fixed classifier leaving the earlier ones nonexistent. This can lead to Differentiated Services code point (DSCP) marking not working as expected.


Example: If the forwarding-class is mapped to some interfaces as below:

set class-of-service interfaces et-0/0/1 scheduler-map TEST-SCHEDULER-MAP
set class-of-service interfaces et-0/0/1 unit 0 forwarding-class TEST-FC-SILVER
set class-of-service interfaces xe-0/0/2 scheduler-map TEST-SCHEDULER-MAP
set class-of-service interfaces xe-0/0/2 unit 0 forwarding-class TEST-FC-SILVER
 

Mitigation:

There will be no impact when the fixed classifier is applied to all interfaces using Xe-*, Et-*, Ae-* in configuration commands like the below and gets changed from one value to another. Logs will be generated but without any impact.

set class-of-service interfaces et-* scheduler-map Test-MAP
set class-of-service interfaces et-* unit 0 forwarding-class Test-class
set class-of-service interfaces xe-* scheduler-map Test-MAP
set class-of-service interfaces xe-* unit 0 forwarding-class Test-class
set class-of-service interfaces all scheduler-map Test-MAP
set class-of-service interfaces all forwarding-class Test-class

 

There will be no impact because the fixed classifier is being changed on all interfaces, so there are no interfaces with a different classifier value available.

Modification History

.