We ran into the same problem.  Here are some options to fix this issue: a) Disable the  ‘proxy arp’ on the L3 device for the 169.254.173.x subnet b)  Create a null route that dumps 169.254.x.x traffic in a black hole, since that subnet should be L2 o...