Description

This article explains the cause for the reported syslog message.

Symptoms

When executing change/delete/remove configurations, and the syslog level is set to error , the following syslog message is reported:

Jul  4 09:26:07  ex3400 dc-pfe: BRCM_NH-,brcm_nh_target_bcast_create(),2377:Unable to get classid for nh 1718
Jul  4 09:26:07  ex3400 fpc0 BRCM_NH-,brcm_nh_target_bcast_create(),2377:Unable to get classid for nh 1718​​

Example: 

root@ex3400# show system syslog 
Jul 04 09:24:21
file messages {
    any critical; 
}

root@ex3400# set system syslog file messages any error  <-- No log output.

root@ex3400# show system syslog 
file messages {
    any error;  <-- changed from 
}

root@ex3400# ... match brcm_nh_target_bcast_create
Jul  4 09:26:07  ex3400 dc-pfe: BRCM_NH-,brcm_nh_target_bcast_create(),2377:Unable to get classid for nh 1718
Jul  4 09:26:07  ex3400 fpc0 BRCM_NH-,brcm_nh_target_bcast_create(),2377:Unable to get classid for nh 1718

Solution

This log message does not impact service and can be safely ignored.  It is expected if target broadcast is not configured.

To suppress repeating non-impacting messages, refer to KB9382 - How to prevent certain syslog messages from being written to the log file [juniper.net]