Some of IPv6 /56 unicast routes are mistakenly treated as multicast routes and programmed against the wrong forwarding entry, causing the IPv6 traffic to be dropped.

re0:evo-pfemand:9924:TRACE_ERR BrcmPfeRt_Error  msg = " RT = BrcmRt, static status_t BrcmRt::handleEvlRouteUpdate(net::juniper::rtnh::Route_h, BrcmUpdateOp) = EVL nexthop-id dont match with the one associated with route, evl nh = 9094, rt NH = 9091"
: No such file or directoryevo-pfemand-sw02.txt:2026-06-11 14:01:13.866473127 re0:evo-pfemand:9953:TRACE_ERR BrcmPfeRt_Error  msg = " RT = BrcmRt, static status_t BrcmRt::handleEvlRouteUpdate(net::juniper::rtnh::Route_h, BrcmUpdateOp) = EVL nexthop-id dont match with the one associated with route, evl nh = 9094, rt NH = 9091"

evopfemand-sw01.txt:2026-06-11 14:11:42.191957973 re0:evo-pfemand:9927:TRACE_ERR BrcmPfeRt_Error  msg = " RT = BrcmRt, static status_t BrcmRt::handleEvlRouteUpdate(net::juniper::rtnh::Route_h, BrcmUpdateOp) = EVL nexthop-id dont match with the one associated with route, evl nh = 9094, rt NH = 9092"

re0:evo-pfemand:9924:TRACE_ERR aft_log_AFT_TRACE_ERROR  log = "[t:9924] [Error] Interface: Failed to get prefix for ifa: irb.548.6:xxxx:xx:x:2401::1

Certain IPv6 routes are configured with a /56 prefix length. Internally, the same /56 length is also used to represent a specific IPv6 multicast (MLD snooping) route type. During normal route programming this is handled correctly, but on the code path that re-processes routes after a reboot, the software was not performing the additional check needed to tell these two cases apart.

As a result, some of these /56 unicast routes (for example the routes pointing traffic to the firewall) were mistakenly treated as multicast routes and programmed against the wrong forwarding entry, causing the IPv6 traffic to be dropped. IPv4 was unaffected because it does not hit this /56 condition.

Other scenarios where this issue could be observed include topology changes, such as link flaps. However, topology changes do not necessarily result in this condition every time and may only trigger it under specific race conditions. This issue is fixed 25.2X100-EVO  and future code versions.  This issue is specific to QFX EVO platforms, and the available fix applies only to those platforms.