FC is an entire high-speed network stack used to implement storage area networks. Starting with vSphere 6.0U2, ESXi supports 32 Gbps FC for all the supported HBA.

When using ESXi with FC SAN, follow the recommendations and best practices of both VMware and the storage vendor to avoid possible issues. Note that storage vendor specifications could be more restrictive than VMware's; for example, the hardware compatibility list could be smallest or restricted on specific firmware/driver versions. In those cases, it's important to use the vendor specifications.

On the ESXi side, you have only to plug the supported FC HBA (with the correct firmware and drivers) and cable them properly, usually following a full fabric topology:

VMware may support point-to-point topologies (such as a DAS storage, for a small environment), but first, you have to verify if the storage vendor supports it.

After that you have only to configure the fabric, with the correct zoning at the port level or better, at World Wide Name (WWN) level (again refer to what your storage vendor requires or recommends); and finally the storage with the correct LUN masking, to present the logical disks to the hosts. At this point there isn't any difference, at ESXi level, between local or remote storage, you just need to format the logical disk from one host and then re-scan the datastore from all the others. That's all!

Most storage requires that each ESXi host is registered with the array, to map correctly the hosts to the arrays and also to authorize the connections (FC does not provide strict authentication capabilities). ESXi usually performs automatic host registration by sending the host's name and IP address to the array, but if you prefer to perform manual registration, you can disable the ESXi auto-registration feature by changing the advanced settings Disk.EnableNaviReg to 0.