text: However, if GM operations experience degraded response times from the secondary system 
  for an extended period, I/O operations begin to queue at the primary system. This queue 
  results in an extended response time to application hosts. In this situation, the 
  **gmlinktolerance**feature stops GM relationships, and the application host’s response time 
  returns to normal. 
  
  After a 1920 event occurs, the GM auxiliary volumes are no longer in the 
  consistent_synchronized state. Fix the cause of the event and restart your GM relationships. 
  For this reason, ensure that you monitor the system to track when these 1920 events occur. 
  
  You can disable the**gmlinktolerance**feature by setting the**gmlinktolerance**value to 0 
  (zero). However, the**gmlinktolerance**feature cannot protect applications from extended 
  response times if it is disabled. It might be appropriate to disable the**gmlinktolerance**feature 
  under the following circumstances: 
  
  (cid:2) During SAN maintenance windows in which degraded performance is expected from SAN 
  components, and application hosts can stand extended response times from GM volumes. 
  
  (cid:2) During periods when application hosts can tolerate extended response times and it is 
  
  expected that the**gmlinktolerance**feature might stop the GM relationships. For example, 
  if you test by using an I/O generator that is configured to stress the back-end storage, the 
  **gmlinktolerance**feature might detect the high latency and stop the GM relationships. 
  
  Disabling the**gmlinktolerance**feature prevents this result at the risk of exposing the test 
  host to extended response times. 