[quote=alankente post_id=820696 time=1601914709 user_id=174460]
We have a Routerboard [1100AHx2] with 6.32.2 router OS
[/quote]
OUCH!! It is time to update that. But of course when it is in a critical place you will need to make sure it will work after the update.
This is a version that is many years old and of course lots of things have changes.
You could consider to use partitioning to setup 2 partitions, copy the current config to the second partition, then update it.
So you can always go back to the 6.32.2 software when you have big problems.
Other than that, there is not much that can be said when you do not include a configuration export in your question.
When you say teaming with ESXi 6.0 do you mean active/passive teaming or LACP?
If I read you right, the default load balance option “original port base” means that each virtual NIC connected to the vswitch is systematically linked to a particular physical NIC (as long as the physical one is up). So on the physical switch, the MAC addresses of various virtual NICs are bound to various switch ports. Hence the ports need to be configured as “edge” ones, i.e. not expect any STP BPDUs to be received. And LACP must not be enabled on the physical switch either, as the VMware vswitch would ignore frames arriving via a “wrong” physical NIC. And if LACP chooses a link within the bond based on source MAC address, as is often the default load distribution strategy, you have your explanation why some PCs cannot ping the VMs which other PCs can…
But as you say that the client PCs have problems to ping each other, the above may not be the reason, or at least not the only one. So what’s the topology, how are the HP boxes connected to each other and to the 1100? A photo of a handmade sketch is normally enough, no need to start visio or alike…