Use the Failover Alert Delay option to change the failover alert delay for a .
The failover alert delay lets you delay the logging of a critical event if the multi-path driver transfers to the non-. If the multi-path driver transfers the logical drives back to the preferred owner within the specified delay period, a critical event is not logged. If the transfer exceeds this delay period, then a logical drive-not-on- alert is issued as a critical event. You can also use this option to minimize multiple alerts when more than one logical drive fails over because of a system error, such as a failed .
The logical drive-not-on-preferred-path alert is issued for any instance of a logical drive that is owned by a non-preferred owner. This alert is in addition to any other informational or critical failover events. Whenever a logical drive-not-on-preferred-path condition occurs, only the alert notification is delayed. A status is generated immediately.
Logical drive path changes that occur as a normal part of a controller download usually do not result in a logical drive-not-on-preferred-path alert notification. After the download completes, the delayed logical drive distribution process is activated. This process determines whether all logical drives were restored to the preferred path during the download. If any logical drives are not on the preferred path, the storage management software logs a critical event and issues an alert notification.
Under , a logical drive-not-on-preferred-path alert might occur after a firmware download completes. This condition occurs if the failover driver is using the non-preferred path because of logical drive ownership changes during the firmware download. The ADT failover driver continues to use the non-preferred path for some period of time, even though the logical drives are restored to their preferred owner. If the driver does not correct itself before the alert delay period expires, a critical event is logged. To prevent unexpected alert notifications, make sure that the alert delay period and the multi-path driver failback probe interval are configured such that the probe runs at least once during the delay period.
Under , such alerts do not occur after firmware downloads. The RDAC failover driver detects logical drive ownership changes and directs I/O down the preferred paths.
To make the best use of the Failover Alert Delay option, set the failover alert delay period such that the host driver failback monitor runs at least once during the alert delay period. A logical drive ownership change might persist through the alert delay period, but the change corrects itself before you can inspect the situation. In such a case, a logical drive-not-on-preferred-path alert is issued as a critical event, but the storage subsystem will no longer be in a Needs Attention state. If a logical drive ownership change persists through the failover alert delay period, refer to the Recovery Guru for recovery procedures.
Keep these guidelines in mind when setting the failover alert delay: