![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||
Solution Type Technical Instruction Sure Solution 2151150.1 : VSM6, VSM7 - What is the replication CLI MIH setting used for in the VSM6 6.3 versions and above?
In this Document
Oracle Confidential PARTNER - Available to partners (SUN). Applies to:StorageTek Virtual Storage Manager System 6 (VSM6) - Version All Versions and laterStorageTek Virtual Storage Manager System 7 (VSM7) - Version 7.0.0 and later Oracle Solaris on SPARC (64-bit) GoalDetermine the use of the CLI MIH setting Understand what the CLI MIH setting does SolutionFrom the 6.3 documentation VSM 6 Installation, Configuration, and Service Guide, the following set mih Command Line Interface (CLI) command was an added feature starting with version 6.3. This value is utilized by Enhanced Replication (synchronous replication) and CLINKs (synchronous replication). Prior to VSM 6.3, an I/O operation was internally timed out in the VSM6 if it did not complete in 40 minutes, regardless of the host Missing Interrupt Handler (MIH) setting. It was recommended to set the host MIH value to 45 minutes. The implementation of the CLI "set mih" command added in 6.3.0.05.000 and above allows each VSM VTSS to override the default 45 minute value to a value between 20 and 45 minutes. Additionally, this value is provided back to the host when the host issues an RCD (Read Configuration Data) operation which the host can then use to override the host's default value MIH setting for this device.
Syntax: set mih -tv value Parameters: This command has one required parameter: -tv The timeout value in minutes. Valid values are from 20 to 45. By default the value is set to 45. Note - The MIH setting does not apply to Asynchronous Replication. The timeout value for this type of replication is 60 minutes. In 7.0.0.07.000 and higher, there is no timeout for slow Asynchornous Replication transfers and the 60 minute timeout does not apply as in previous versions of code. A timeout for Asynchronous Replication is still possible if no progress in replication transfers are being made. References<BUG:23607743> - QUESTIONS REGARDING CLINK AND RLINK REPLICATION TIMEOUT VALUEShttp://amomv0115.us.oracle.com/archive/cd_ns/E38194_02/en/E65761/E65761_02.pdf Attachments This solution has no attachment |
||||||||||||||||
|