I’ve had this question a few times, if you enable vSAN File Services and you use NSX-T and it’s not possible to reach the vSAN File Service IP addresses, what should you do? In 999 out of the 1000 cases, it typically is a matter of enabling Mac Learning on the Segment Profile for the segment being used by vSAN File Services. I stole the below screenshot from William, it shows you how to enable it.
You may wonder why this needs to be enabled, well basically because the vSAN File Services VM is not what you are directly communicating with. The IP Address and MAC address you communicate with is associated with the vSAN File Service protocol stack container. As a result, MAC Learning needs to be enabled. I described this already in my FAQ post, but as it comes up frequently I figured I would dedicate a post to it.