ACX7024 is reporting repeated Broadcom ASIC programming failures while creating MPLS VPN tunnel encapsulations.
May 28 17:13:00 Router evo-pfemand[7886]: [t:7886] [Error] brcm-sdk : dnx_algo_gpm_gport_to_global_resources: Error 'Invalid parameter' indicated, gport given is invalid when trying to map gport to lif, gport (0xffffffff)
May 28 17:13:00 Router evo-pfemand[7886]: [t:7886] [Error] brcm-sdk : dnx_algo_gpm_gport_to_hw_resources: Error 'Invalid parameter' indicated ;
May 28 17:13:00 Router evo-pfemand[7886]: [t:7886] [Error] brcm-sdk : dnx_mpls_tunnel_initiator_create_verify: Error 'Invalid parameter' indicated ;
May 28 17:13:00 Router evo-pfemand[7886]: [t:7886] [Error] brcm-sdk : bcm_dnx_mpls_tunnel_initiator_create: Error indicated (Invalid parameter) on VERIFY ;
May 28 17:13:00 Router evo-pfemand[7886]: EVO_PFEMAND_ASIC_PROGRAM_FAILED: Failed to program the hardware with an error - invalid parameters specified
May 28 17:13:00 Router evo-pfemand[7886]: [t:7886] [Error] Broadcom : BrcmErrorMsg: Failed to program the hardware with an error - = invalid parameters specified, during = jbcm_mpls_tunnel_initiator_create
May 28 17:13:00 Router evo-pfemand[7886]: [t:7886] [Error] NH : BrcmPlusNhMplsVpn: status_t BrcmPlusNhMplsVpnHwList::createEntryInHw(uint32_t, BrcmPlusNhEncapAccessList&) = mpls encap create failed, unit = 0, Error = Invalid parameter
May 28 17:13:00 Router evo-pfemand[7886]: [t:7886] [Error] NH : BrcmPlusNhMpls: status_t BrcmPlusNhMplsVpnHwList::create() = mpls encap create hw basic
May 28 17:13:00 Router evo-pfemand[7886]: [t:7886] [Error] NH : BrcmPlusNhMplsVpn: mpls vpn failed to program the hardware = { tnlIntfIdx 0 : 950811}, ]
May 28 17:13:00 Router evo-pfemand[7886]: [t:7886] [Error] NH : BrcmPlusNhMplsVpn: status_t BrcmPlusNhMplsVpn::vpnHwCreate(BrcmPlusNhMplsVpnDataShrPtr&) = vpnJ2EncapHwCreate failed, nhIndex = 8725
May 28 17:13:00 Router evo-pfemand[7886]: [t:7886] [Error] compName = "NH", ddsType = "Indirect" tpName = "BrcmPlusNhIndirect", guid = "760210706115" msg = " nhIndex = 8725, nhToken = 537028034, proto = ipv4->mpls, tnl fec id = 537078736"
May 28 17:13:00 Router evo-pfemand[7886]: [t:7886] [Error] compName = "NH", ddsType = "Indirect" tpName = "BrcmPlusNhIndirect", guid = "760210706115" msg = " nhIndex = 8725, nhToken = 537028034, proto = ipv4->mpls, NH-Token = = 537028034, Op = Add Indirect Chain"
May 28 17:13:00 Router evo-pfemand[7886]: [t:7886] [Error] NH : BrcmNhGeneric: static status_t BrcmNhGeneric<BrcmParamsType, BrcmNhType>::create(const BrcmParamsType&) [with BrcmParamsType = std::shared_ptr<BrcmParamsNhIndirect>; BrcmNhType = BrcmNhIndirect; status_t = int] = Failed to create entries in HW for NH Modify, nhIndex = 8725, nhType = 6
May 28 17:13:00 Router evo-pfemand[7886]: [t:7886] [Error] compName = "NH", ddsType = "Nexthop" tpName = "BrcmNhIndirect", guid = "760210706112" msg = " nhIndex = 8723, proto = ipv4, Failed to create _brcmPlus NH object for type = TunnelService"
The issue arises when transitioning the transport path to SR-TE for services utilizing SR-TE as the underlay, which modifies the next-hop by introducing an additional next-hop required for SR-TE.
This change requires an MBB update in the forwarding plane (PFE) to ensure seamless traffic switchover.
However, due to the MBB update not being handled correctly in the PFE, traffic blackholing occurs during the transition for any service with underlay as SR-TE.
This issue happens when the "preserve-nexthop-hierarchy knob is configured.
This issue might be seen if the following conditions are met:
* On Junos OS Evolved ACX platforms* SR-TE is configured
* Transitioning the transport path to SR-TE for services utilizing SR-TE as the underlay
* Knob "preserve-nexthop-hierarchy is configured
This is fixed via PR1890392.