Is it platform specific

generic

Importance or Severity

Medium

Description of the bug

On dT2 during ACL tests, after reboot or port toggle resets the BGP connections, if a test tries to verify a packets expected route through the dT2 too soon after the toggle, the device may send it through the wrong route or drop the packet. We see that for some T2 we need this change as well, we suspect this is due to a high number of routes

Steps to Reproduce

Mimic the ACL test on a device with many routes advertised to it (T2/dT2 typically): send a packet with a destination IP with an expected downlink route through uplink shortly after BGP comes up, after port toggle or reboot.

We see it rarely when running the ACL test (hard/time-consuming to reproduce individually, but running the whole suite tends to get at least 1 or 2 errors), resulting in errors such as: Did not receive expected packet on any of ports [...] and Received expected packet on port X for device 0, but it should have arrived on one of these ports: [...]

Actual Behavior and Expected Behavior

The route the packet takes should be as expected

Relevant log output

N/A

Output of show version

20250305

Attach files (if any)

No response