Post upgrading to ESXi 7.0 and above, Some SAS paths of LUN under lsi_msgpt3 / lsi_msgpt35 controller cannot be identified.
Article ID: 312116
Updated On:
Products
Issue/Introduction
- In the Dell EMC Storage Compatibility Matrix, the 6.5 VMWare ESXi version is tested / supported with SAS front end connectivity.
- SAS driver "lsi-msgpt3"/"lsi_msgpt35" and SCOS Versions 7.2.x and 7.3.x were included in this, tested and supported solution.
- However, upgrades to VMWare ESXi 6.5 U1, 6.5 U2, and 6.7 automatically install updated lsi-msgpt3 / lsi-msgpt35 SAS drivers, such as Version 16. Without manual intervention of configuring a module parameter on the driver, lsi-msgpt3//lsi-msgpt35 does not work properly (e.g., rebooting host sees LUN capacity of 0 bytes, loses access to SAS Front End volumes upon controller failover) with ESXi 6.5 and SCOS.
Symptoms:
The 12gb SAS HBA registers primary and secondary failover LUNS. It has (2) SAS circuits to the Storage Provider.
Post the update to 7.0U3c, only half of the LUNs showed up (some were primary some were secondary). The LUNS that are registered as secondary, no longer mount.
Environment
VMware vSphere ESXi 7.0.x
Cause
Storage Center systems with Front End SAS connectivity have been officially tested and supported to work with ESXi version 6.7 . If you encounter issues with ESXi 6.5 and SCOS 7.2 / 7.3, then the best practice setting is to modify the module parameters for all versions of the lsi-msgpt3 / lsi-msgpt35 SAS driver.
Resolution
Follow the below steps:
1. List out the module parameter values (take lsi_msgpt3 driver for example)
esxcli system module parameters list -m lsi_msgpt3
2. Modify the issue_scsi_cmd_to_bringup_drive module parameter.
esxcli system module parameters set -p issue_scsi_cmd_to_bringup_drive=0 -m lsi_msgpt3
3. Validate that the module parameter value has been modified with the list command in Step 1.
4. Reboot the ESXi host for the changed value to take effect.
Feedback
