-
Unfortunately after upgrading the nfnic driver the option to set that parameter won't be available, it will only be configurable after the first reboot completes. Once the ESXi hosts is back online reconnect via CLI and check that the nfnic module parameters are available.
[root@ESXi-3:~] esxcli system module parameters list -m nfnic Name Type Value Description ------------------------ ----- ----- -------------------------------------------------------------- lun_queue_depth_per_path ulong nfnic lun queue depth per path: Default = 32. Range [1 - 1024] -
Note that the default value is 32, but can be configured up to 1024. Set the value to 128 in the event that vSphere Virtual Volumes are being used in the environment. The value can be set higher or lower as needed, but 128 is recommended when using VVols.
[root@ESXi-3:~] esxcli system module parameters set -m nfnic -p lun_queue_depth_per_path=128 [root@ESXi-3:~] esxcli system module parameters list -m nfnic Name Type Value Description ------------------------ ----- ----- -------------------------------------------------------------- lun_queue_depth_per_path ulong 128 nfnic lun queue depth per path: Default = 32. Range [1 - 1024] [root@ESXi-3:~] esxcli storage core device list -p naa.624a937016d9d3754f8a461800011016 Display Name: PURE Fibre Channel Disk (naa.624a937016d9d3754f8a461800011016) ... Device Max Queue Depth: 32 No of outstanding IOs with competing worlds: 32 [root@ESXi-3:~] esxcli storage core device set -O 128 -d naa.624a937016d9d3754f8a461800011016 Unable to set device's sched-num-req-outstanding. Error was: Cannot set device queue depth parameter. sched-num-req-outstanding should be <= 32 -
The ESXi host will need to be rebooted for the parameter change to take effect. As shown above the device setting can not have the setting increased until after the reboot.
[root@ESXi-3:~] esxcli system shutdown reboot --reason "nfnic parameter update" - After the ESXi host is back online, the PE Device Queue Depth can be increased.