ESX requires HBAs and that's it. ESX already has 'drivers' within its hypervisor that is needed to communicate with the SAN. For example, for EMC, you needed 'Powerpath' on a Windows host to communicate with an EMC SAN. You don't need to install Powerpath on ESX because it's part of the drivers within the hypervisor. So, all you need is the connections to the SAN -> fibre cables, SAN Switches and the FC SAN itself (which you say FC switches/SAN is being installed?). The HBA model drivers are also within ESX (e.g. QLogic HBA driver).
For the host to then be 'seen' on the SAN, you need to configure zoning on your SAN switch. What this does is reconcile the HBA WWN (world wide name) to a path on the SAN. You configure a Zone for each connection on each host for failover/redundancy. Zoning configuration is different for each SAN Switch so consult your SAN switch vendor (Brocade, Cisco, etc.) for explicit details on that part. Once Zoning on the Switches is completed, you then need to make your ESX hosts 'viewable' on your SAN. Again, that is also dependent on the SAN vendor. For me, I use EMC CX4-120, so I use Navisphere, a web-based GUI to configure my hosts to be 'seen' on my SAN. In the newer EMC SANs, hosts are detected automatically now (thank heavens!) :)
Once your host is detected, it's then a matter of creating a storage group on your SAN, assigning multiple ESX to that storage group, creating RAID Groups, then LUNs within the RAID Groups, then assigning those LUNs to the Storage Group that the ESX hosts are assigned to. You then log in to vSphere with the Client, rescan your HBAs and there you go...your shared storage with show (going through the 'Add Storage' wizard).
Hope that helps.
~coolsport00
