• Digital Workspaces
          • Digital Workspaces

            Enable desktop & application virtualization, identity management, and secure remote access for work from home (WFH) employees

          • zPortal
          • Controller for desktop and application virtualization via shared hosted desktops and VDI

          • zGateway
          • Secure remote users working from any network on any device to protect corporate data

          • SnapVDI Thin Client (zTC)
          • Thin client endPoint devices for Citrix, Microsoft Hyper-V & WVD and VMware

          • zBrows
          • Provide secure browser-based access to virtualized corporate workspace users

          • zMFA
          • Integrated multi-factor authentication (MFA) for secure user verification on any device

          • zClient
          • Software client for installing on your endpoint devices for connection to zPortal and zGateway

    • Healthcare Solutions
          • Healthcare Solutions

            Remote patient monitoring platform and devices for clinicians and caregivers to remotely monitor the vital signs of their patients

          • ZettaRPM
          • Universal cloud-based remote patient monitoring platform for healthcare organizations

          • B.O.L.T Devices
          • Monitor, track, and improve patients’ health with remote patient monitoring (RPM) devices

    • Data Storage Appliances
          • Data Storage Appliances

            Reliable, high-performance SAN appliances with inclusive snapshots, replication, and  automated data tiering software

          • StorTrends 3500i
          • Extreme-performance SAN with Hybrid and All-Flash configurations to handle even the most demanding workloads

          • StorTrends 3400i
          • Highly reliable HDD-based SAN suited for data retention, backups and low-performance environments

          • StorTrends 3202j
          • Expansion shelf configurable as all-HDD, hybrid, or all-flash to seamlessly add capacity to the StorTrends 3500i or StorTrends 3400i

  • Knowledge Base
  • Company
  • Events
  • Support
  • Contact
  • Partner Portal

How Can We Help?

StorTrends Timeouts

You are here:
< All Topics

Hypervisors

Any
Always install client tools for the VM’s if available.
VMWare
For software iSCSI Adapter set the Configuration->Storage Adpaters->Software iSCSI Adapter->Properties->Advanced->Recovery Timeout to 120 seconds.

NOTE: After modifying the iSCSI Adapter “RecoveryTimeout” value, the ESX iSCSI Initiator MUST disconnect and reconnect all StorTrends targets, or simply reboot the ESX server for the change to take effect.

HyperV
Follow the Windows recommendations below
Citrix
Follow the Linux recommendations below

Windows (all versions)

Any system which uses a StorTrends drive either directly or indirectly
This value should be set for both virtual and physical machines whose underlying drive is a StorTrends iSCSI drive even if passed through a hypervisor.
Change the registry key HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Disk/ TimeOutValue to be 190 seconds (BE in hex).* If it is not present, please create the DWORD entry.

NOTE: After changing settings in the registry the Windows server MUST be rebooted for the changes to take effect.

Additional settings when connecting to a StorTrends drive via Microsoft iSCSI Initiator

These additional registry key changes are for both physical and virtual machines connecting to StorTrends targets via a Microsoft iSCSI Initiator. All other registry settings related to the Microsoft iSCSI Initiator should be left at the default settings. Please refer the Microsoft iSCSI initiator User Guide for default values.
Example: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e97b-e325-11ce-bfc1-08002be10318}\<instance number>\Parameters

Set LinkDownTime to 180 seconds (B4 as hex).*
Set MaxRequestHoldTime to 180 seconds (B4 as hex).* Set SrbTimeoutDelta to the default 15 seconds (F as hex).*
On Windows 8/Windows Server 2012 systems: set the ErrorRecoveryLevel to 0 (zero) to ensure that the initiator reconnects reliably.*
These values may occur multiple times in the registry. Please set all of them the same.

NOTE: After changing settings in the registry the Windows server MUST be rebooted for the changes to take effect.

Like Disk TimeoutValue for NAS volumes, SMB SessTimeout should be set to 200 seconds on the registry / Request Expiration Timer [MS-SMB2] /Client session timeout (SMB1)

This is the amount of time the client waits for the server to respond to an outstanding request. This timeout value can be adjusted through the following registry setting:
\HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\SessTimeout
Value type: Dword
Decimal Value: 200

Error while copying data to NAS share “Error 0x8007003B unexpected network error”

Increase the timeout setting to 600, if Windows reported “0x7008003B” error code.
From Windows power shell, run “Set-SmbClientConfiguration -SessionTimeout 600”
OR,
Edit the registry to update the following parameter:
\HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\SessTimeout
Value type: Dword
Decimal Value: 600

NOTE: After changing settings in the registry the Windows server MUST be rebooted for the changes to take effect.

Linux

Any system which uses a StorTrends drive either directly or indirectly

When connecting to a StorTrends target the block device timeout needs to be modified to 190 seconds. It needs to be greater than the replacement_timeout value. If being connected to via a Hypervisor as a VM hard drive please use the tools recommended by the Hypervisor as the udev ‘vendor’ and ‘model’ attribute values may be different. E.g. VMTools creates an udev rule for VMDKs with the appropriate timeout as VMDKs have different ‘vendor’ and ‘model’ attributes than StorTrends iSCSI drives.
* This can be done manually each time the target is connected to by running echo 190 > /sys/ block/<device name>/device/timeout. Where, the device name will be known only after the login.
* To automatically set this value when an iSCSI login happens, such as persistent targets during reboot, add a new udev rule. In most distoro’s the path will be /etc/udev/rules.d/99-stortrends-scsi-udev.rules. The new udev rule will only work for new connections; any existing connections will either require a logout/login of the target or the aforementioned manual method.
* UDev rule for Citrix VDisk’s: #Citrix VDisk
ACTION==”add”, SUBSYSTEMS==”scsi”, ATTRS{vendor}==”QENU” , ATTRS{model}==”QEMU HARDDISK”, RUN+=”/bin/sh -c ‘echo 190 >/sys$DEVPATH/device/timeout’”
* UDev rule for RedHat/Fedora and SuSE 11.2 OS: #StorTrends iSCSI
ACTION==”add”, SUBSYSTEMS==”scsi”, ATTRS{vendor}==”AMI” , ATTRS{model}==”StorTrends iTX”, RUN+=”/bin/sh -c ‘echo 190 >/sys$DEVPATH/device/timeout’”
Additional settings when connecting to a StorTrends drive via OpenISCSI
This value should be set for both virtual and physical machines whose underlying drive is a StorTrends
iSCSI drive. The default configuration file path is “/etc/iscsi/iscsid.conf”. Any existing iSCSI connections will have to be disconnected and removed from the iscsiadm database then logged back into for the new setting to take effect.
– Set node.session.timeo.replacement_timeout to 180 seconds.

Tags:
Was this article helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
How can we improve this article?
Table of Contents
Top