Hmmm, something else I notice which seems to be causing issues is that the MAC address changes on my internal VLAN after joining the virtual device to the cluster.
internal Link encap:Ethernet HWaddr 00:50:56:AC:6E:68
inet addr:192.168.167.251 Bcast:192.168.167.255 Mask:255.255.254.0
inet6 addr: fe80::298:76ff:fe54:3210/64 Scope:Link
inet6 addr: fe80::250:56ff:feac:6e68/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4205 errors:0 dropped:0 overruns:0 frame:0
TX packets:426 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2731292 (2.6 MiB) TX bytes:23383 (22.8 KiB)
internal Link encap:Ethernet HWaddr 00:50:56:AC:40:83
inet addr:192.168.167.251 Bcast:192.168.167.255 Mask:255.255.254.0
inet6 addr: fe80::298:76ff:fe54:3210/64 Scope:Link
inet6 addr: fe80::250:56ff:feac:4083/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19243 errors:0 dropped:0 overruns:0 frame:0
TX packets:2455 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13927378 (13.2 MiB) TX bytes:165984 (162.0 KiB)
Immediately after this happens, I cannot ping the gateway, other peer on that interface. The second MAC address doesn't match the MAC on the vmware server (so definately doesn't work!)