Multiple vKernel interfaces on the same subnet causing this was a known problem, and fixed in 5.5 U1 - hence my confusion on why it was happening now.
Also, re-updating was always going to be required after discovering the root cause.
See my reply below and you will understand the silliness that caused this.