Description

This article explain the L2CKT issue where L2CKT connection is up on both side but traffic is not flowing. There is no egress traffic on access interface unit.

Symptoms

The issue can be seen on core link flap in the network or new L2CKT configuration. Below logs will be seen during the issue time.

 

1st issue logs:- 

Feb 4 15:26:19 ACX7100-EVO evo-pfemand[9691]: %USER-3: [Error] BrcmPlusPfe: bcm_vlan_port_create, ret = -8 : Entry exists

Feb 4 15:26:19 ACX7100-EVO evo-pfemand[9691]: %USER-3: [Error] BrcmPlusIf: Unit:0 Lif:1149370367 Creation for ifl:11874 failed, Entry exists

Feb 4 15:26:19 ACX7100-EVO evo-pfemand[9691]: %USER-3: [Error] BrcmPlusIf: BrcmPlusJ2Ifl::BrcmPlusJ2Ifl(BrcmParamsIflPtr&)Failed to install lif for ifl:11874

Feb 4 15:26:19 ACX7100-EVO evo-pfemand[9691]: %USER-3: [Error] BrcmPlusIf: Unit:0 bcm_vlan_port_translation_set Failed, error:-1 ,Internal error IFLIndex:11874 GportNum:1149370367 vlan_translation_type:4 ovid:0 ivid:0

Feb 4 15:26:19 ACX7100-EVO evo-pfemand[9691]: %USER-3: [Error] BrcmPlusIf: status_t BrcmPlusIfl::iflInstallIngressXlateEntry(int)INGRESS Vlan Map Xlate Failed, IFL_idx:11874 Ovid:0 Ivid:0 rw_opcode:VTagPop num_Tags:1 IveID:^B Unit:0

Feb 4 15:26:19 ACX7100-EVO evo-pfemand[9691]: %USER-3: [Error] BrcmPlusIf: static int BrcmPlusIflApi::installVlanXlateEntry(uint32_t, int, VlanMapsAppType, uint32_t)Failed to install Ingress xlate entry for ifl:11874

Feb 4 15:26:20 ACX7100-EVO evo-pfemand[9691]: %USER-3: [Error] BrcmPlusCos: static int BrcmPlusClassifierProfile::set_lif_classifier(int, int, int)Failed to set qos profile: 10030005, to ifl gport: 4481fffferror: fffffffc, Invalid parameter unit: 0

Feb 4 15:26:20 ACX7100-EVO evo-pfemand[9691]: %USER-3: [Error] BrcmPlusCos: int BrcmPlusCosHwProfile::bindQosHwProfileToLif(int, int), Failed to bind profile on ifl:11874, unit:0

Feb 4 15:26:20 ACX7100-EVO evo-pfemand[9691]: %USER-3: [Error] BrcmPlusCos: status_t BrcmPlusCosHwProfile::bindHwProfiletoIfl(int, int), failed to rebind rewrite profile to LIF. ret:-1

 

 

2nd issue journal_ctl logs:- 

 

2026-02-24 10:53:32.834101355 re0:evo-pfemand:8246:TRACE_ERR BrcmPfe_TP_Obj_Error compName = "RT", ddsType = "RouteMpls", tpName = "BrcmPlusRtMplsVpnHandler", guid = "764515992987", msg = " = mpls_port_add failed in inLabelMplsPortUpdate for, Unit = 0, error = -8"

 

 

Enable below debug logs during the issue time to get the complete logs:-

 

set system trace application evo-pfemand node re0 level debug

show trace application evo-pfemand | save /var/tmp/evo-map.log

 

Solution

This is due to a bug where allocated lif indices are not freed up correctly So, it might release a wrong lif index 
( which is still under use ) which is then getting allocated. This is the root cause for both the issues.

1) vlan_port_create() -> entry exists error
2) mpls_port_add() -> entry exists error This is fixed via RLI and fix is only available from 24.3 onwards

Modification History

2026-03-25 : Article Created