Description

[QFX]BRCM_NH-,brcm_nh_l3_hw_install(),968:bcm l3 egress create object failed for nh 2869 (-15:Invalid configuration)

Symptoms

This article explains the following syslog message on QFX5100-VCF:

 

BRCM_NH-,brcm_nh_l3_hw_install(),968:bcm l3 egress create object failed for nh 2869 (-15:Invalid configuration)

 

Solution

Whenever these messages generated on a VCF setup, we may observe incremental Drops and we could find from the "show interface extensive" output

 

user> show log messages | match "BRCM_NH"

fpc0 BRCM_NH-,brcm_nh_l3_hw_install(),968:bcm l3 egress create object failed for nh 2869 (-15:Invalid configuration)                    pfe:0, port:0, vlan:0, l3-intf:0 flags: 0 unit 0

fpc4 BRCM_NH-,brcm_nh_l3_hw_install(),968:bcm l3 egress create object failed for nh 2869 (-15:Invalid configuration)                    pfe:0, port:0, vlan:0, l3-intf:0 flags: 0 unit 0

fpc5 BRCM_NH-,brcm_nh_l3_hw_install(),968:bcm l3 egress create object failed for nh 2869 (-15:Invalid configuration)                    pfe:0, port:0, vlan:0, l3-intf:0 flags: 0 unit 0

fpc4 BRCM_NH-,brcm_nh_l3_ucast_action(),1392:(reason: 4294967281) hw nh 2869 handling failed

fpc5 BRCM_NH-,brcm_nh_l3_ucast_action(),1392:(reason: 4294967281) hw nh 2869 handling failed

fpc5 BRCM_NH-,brcm_nh_ucast_install(),1331:Reason (null): Err Code: -15)

fpc4 BRCM_NH-,brcm_nh_ucast_install(),1331:Reason (null): Err Code: -15)

 

Input errors:

   Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Bucket drops: 0, Policed discards: 0, Resource errors: 0

 Output errors:

   Carrier transitions: 2, Errors: 0, Drops: 3474396, MTU errors: 0, Resource errors: 0, Bucket drops: 0

 Egress queues: 12 supported, 5 in use

 

As per the above log messages, it indicates that the VCF setup has invalid configuration.

 

In order to fix the issue we need perform "commit synchronize" which helps us to resolve the invalid configuration issue. Post which we didn't observe any drops and the services were restored.

 

user# commit synchronize

 

In case the issue is still observed, then contact JTAC Support for further investigation.

Modification History

2023-11-22 : Article Created