This reminds me of a similar situation you had earlier this year, where not all VMs were responding to pings. Do you recall what the issue was there and how you resolved it?
In looking at your output, specifically "Client0 : All pings failed at 10.253.43.11", please try to troubleshoot that error by powering up the Client0 VM and ping that IP address manually from the PrimeClient VM. There is definitely some underlying issue with the networking in your lab environment (DHCP server, virtual distributed switch, physical NICs). I know you said there were no IP address conflicts, but it wouldn't hurt to double check everything once more, and if possible, recreate a new virtual distributed switch from scratch if feasible.
Yes we had a problem where the network team had to allow pings between the client cluster and the tile cluster from what I remember but I think all tile VMs were unpingable. This time, some are, some are not.
I've got a quick call with the team tomorrow so I'll get them to check it out again as it is a different cluster and subnets for an AMD cluster so possibly the same thing has happened.
Definitely looks like a networking issue the physical side as everything else looks great
I'll post back with a resolution when we sort it :-)
Interestingly, the network and config was all fine but it seemed like there was a stale arp cache on the hosts which was causing the issues.
I refreshed the cache on the vCenter using systemctl restart dnsmasq and had to refresh the physical and vmkernel networking of all the hosts within vCenter.
The first tile vms then deployed fine without any pinging issues.