Parameter for monitoring recovery from a failure

Provisioning Guide for Open Systems for VSP One Block 85

Version
10.5.x
FileSize
3643 KB
Audience
anonymous
Part Number
MK-26VSP1B033-03
ft:lastEdition
2026-06-23
Product
SVOS

In your host OS and multipath software, set the time for monitoring recovery from a failure. If an alternate LU path fails during reboot for microcode update or during reset due to a failure, both the original path and alternate path become temporarily inaccessible until the reboot or reset is completed. The 25-Gbps Ethernet channel board requires approximately 130 seconds at maximum before I/O restart for reboot during update of its microcode or for reset if a failure occurs. To continue host I/O during this time, configure the parameter settings to change the time for monitoring recovery from a failure.

I/O might stop in the following circumstances:

  • If the single path configuration is used, host I/O might stop, or a host I/O error might occur because the 25-Gbps Ethernet channel board cannot continue host I/O for a maximum of 130 seconds during reboot for microcode update or during reset due to a failure.
  • If the parameter for monitoring recovery from a failure is not configured and an alternate LU path fails during reboot for microcode update or during reset due to a failure, I/O might stop or a host I/O error might occur.

The relevant parameter must be configured for the following host OSs and multipath software:

  • Windows Server (Microsoft DSM/MPIO or Hitachi Dynamic Link Manager)
  • Red Hat Enterprise Linux (Device Mapper Multipath or Hitachi Dynamic Link Manager)
  • SUSE Linux (Device Mapper Multipath or Hitachi Dynamic Link Manager)

If VMware uses a guest OS iSCSI initiator, you need to configure the relevant parameter in the guest OS (Windows, Red Hat Enterprise Linux, or SUSE Linux).

When you use VMware ESXi as the iSCSI initiator, you do not need to configure the parameter.