In the Host Configuration Guide, on page 59, it talks about setting the LUN queue depth on the Emulex HBA to 128.
The document also has a table that prescribes settings for a mixed storage environment. (in my case, XIO and VNX)
That table has no recommendation for LUN queue depth on the HBA module. It does talk about the per LUN SchedNumReqOutstanding parameter, which I would set to 256 for all XIO LUNS.
My question is, with a mixed storage environment, should I be adjusting the HBA LUN queue depth to the prescribed XIO settings or leaving them at the default (which I think in this case is 30)
Because you reference schednumreqoutstanding parameter, i am assuming you are trying to achieve this in a VMware environment. For queue depth there are two settings that can be adjusted: LUN Queue Depth, and HBA Queue Depth (IO throttle count). For Emulex, XtremIO best practice recommendation is to set HBA Queue Depth to 8192(default), and Lun Queue depth to 128. However, since your vhbas also have VNX, you need to go with lowest value which would be of VNX. Therefore, you would set Lun Queue Depth to 32, and HBA queue depth (if same vhba as VNX) to the VNX one. However, since you are using Emulex, and Emulex HBAs typically have the driver for these HBAs preloaded with ESX, you can stay with the default of 8192.
mabela
33 Posts
5290
0
Posted July 5th, 2017 10:00
Because you reference schednumreqoutstanding parameter, i am assuming you are trying to achieve this in a VMware environment. For queue depth there are two settings that can be adjusted: LUN Queue Depth, and HBA Queue Depth (IO throttle count). For Emulex, XtremIO best practice recommendation is to set HBA Queue Depth to 8192(default), and Lun Queue depth to 128. However, since your vhbas also have VNX, you need to go with lowest value which would be of VNX. Therefore, you would set Lun Queue Depth to 32, and HBA queue depth (if same vhba as VNX) to the VNX one. However, since you are using Emulex, and Emulex HBAs typically have the driver for these HBAs preloaded with ESX, you can stay with the default of 8192.