PowerCLI Script – HPE Nimble iSCSI LoginTimeout NoopOutTimeout NoopOutInterval

Per https://infosight.hpe.com/InfoSight/media/cms/active/public/pubs_VMware_Integration_Guide_NOS_50x.whz/cwz1530912931494.html you should change the Host Disk Timeout Values to 30 seconds as HPE Nimble iSCSI best practice on the ESXi host.

Defaults for a fresh ESXi 6.5 install are not 30 for: LoginTimeout 5 / NoopOutInterval 15 / NoopOutTimeout 10

Granted the HPE Nimble Storage Connection Manager for VMware (NCM) “should” set them to 30 if the version is 6 or higher, but in my testing it did not (see screen cap below for ESXi 6.7 and nimble-ncs nimble-psp 7.0.0-650012)

The PowerCLI script will filter for Connected ESXi hosts in a specific Cluster and use get-esxcli v1 to change the LoginTimeout NoopTimeout NoopInterval values to 30 seconds and get-esxcli v2 to validate.
You will need to reboot the ESXi hosts for the new values to take effect (2 birds, 1 stone during the next VUM patching window).

Tip – You can remove the “# Change” section of the script (lines 22-41) to Report only.

Thanks https://encoretechnologies.github.io/blog/2020/03/vmware-iscsi-timeout/ for pointing me in the right direction.

Manual way: (note – a reboot is still needed even though the new value is 30)
You can change these by hand in the web client. Storage / Storage Adapters / Advanced Options – search via chrome for LoginTimeout / NoopInterval / NoopTimeout

 

Validate via a putty session to the ESXi host. (change vmhba65 to your correct #) 1st # is the current.
esxcli iscsi adapter param get -A vmhba65 | grep ‘LoginTimeout\|NoopOutTimeout\|NoopOutInterval’

 

Setup

Per https://infosight.hpe.com/InfoSight/media/cms/active/public/pubs_VMware_Integration_Guide_NOS_50x.whz/cwz1530912931494.html you should change the Host Disk Timeout Values to 30 seconds as HPE Nimble iSCSI best practice on the ESXi host.

Defaults for a fresh ESXi 6.5 install are not 30 for: LoginTimeout 5 / NoopOutInterval 15 / NoopOutTimeout 10

Granted the HPE Nimble Storage Connection Manager for VMware (NCM) “should” set them to 30 if the version is 6 or higher, but in my testing it did not (see screen cap below for ESXi 6.7 and nimble-ncs nimble-psp 7.0.0-650012)

Scoop

The PowerCLI script will filter for Connected ESXi hosts in a specific Cluster and use get-esxcli v1 to change the LoginTimeout NoopTimeout NoopInterval values to 30 seconds and get-esxcli v2 to validate.
You will need to reboot the ESXi hosts for the new values to take effect (2 birds, 1 stone during the next VUM patching window).

Tip – You can remove the “# Change” section of the script (lines 22-41) to Report only.

Thanks https://encoretechnologies.github.io/blog/2020/03/vmware-iscsi-timeout/ for pointing me in the right direction.

Manual way: (note – a reboot is still needed even though the new value is 30)
You can change these by hand in the web client. Storage / Storage Adapters / Advanced Options – search via chrome for LoginTimeout / NoopInterval / NoopTimeout

 

Validate via a putty session to the ESXi host. (change vmhba65 to your correct #) 1st # is the current.
esxcli iscsi adapter param get -A vmhba65 | grep ‘LoginTimeout\|NoopOutTimeout\|NoopOutInterval’

Script

[crayon-5fc3aed09d48a711436230/]

 

Menu