Best practices for HSX SAN mapping

Hello @ivanalvarez 

Can you use the following commands to confirm that the datastores can be seen by the HS nodes?

https://documentation.commvault.com/2024/expert/vmfssaninfo_tool.html

shell ./VMFSSanInfo datastore

I’m guessing the answer is no and with the rescan not working either we need to validate we can talk to the hosts on port 443 and 902. 

This link has all the requirements and is a good one to check and confirm you have not missed anything simple: 

https://documentation.commvault.com/2024/expert/san_transport_for_vmware.html

Kind regards

Albert Williams

Hi @Albert Williams

Thanks for the tip.
However, even though we see the datastores with the tool you mentioned, and both SAN zoning and LUN mapping look correct, we still have issues running jobs with SAN transport mode.

Errors are not helping really, as we still see the “Failed to read disk over SAN” and we believe at this point it could be VMWare related.
We have a case with CommVault Support and have uploaded some logs.
I will keep you posted.

Regards
Ivan

What does ./VMFSSanInfo datastores return?

@Paul K it returns a complete list of “PhysicalDisk” and “Datastore Name”.

However it reports some errors about “Datastore ( XXXX ) has too many extents, check multipath settings and snapshots.” But I have already reviewed the entire SAN environment with the Storage guys and they can’t find any issues with the SAN zoning or the LUN mapping. Everything looks correct and the settings are as per Best Practices (Hitachi storage behind).

Commvault Support believes it’s related to a VMWare known issue “DiskLib error 4096062” once reviewed the VixDiskLib.log.