We saw this same issue and it was the oddest ever. We found using a /22 for the VLAN interface caused the issue. The issue is gone just by changing the interface to a /24 or /21 (please consider the network implication before doing this).
... View more
