Filter
Top Products
5–120 CLI Commands
SET NOFAILOVER
Reconfigures both controllers to operate in a nondual-redundant (nonfailover)
configuration. Immediately after entering this command, remove one controller from
the shelf because the sharing of devices is not supported by nonredundant controllers.
NOTE: SET NOFAILOVER and SET NOMULTIBUS_FAILOVER have the same effect.
Either command exits from transparent or multiple bus failover mode.
It is recommended that both controllers be present when this command is carried out.
Otherwise, the controllers become misconfigured with each other, requiring
additional steps later to allow the “other controller” to be configured for failover.
This command affects both controllers, regardless of the controller on which the
command is carried out. All units accessed through the “other controller” failover to
“this controller” and the “other controller” is shut down. No configuration
information is lost when the SET NOFAILOVER command is carried out.
Syntax
SET NOFAILOVER
Switches
DESTROY_UNFLUSHABLE_DATA
NODESTROY_UNFLUSHABLE_DATA (Default)
Instructs the controller how to handle unflushable data contained within the write-
back cache. Unflushable data may be present if, for example, a member of a stripeset
has failed. If the other controller is not running, use this switch to specify how to
handle this unflushable data when taking the controller pair out of failover mode. If
the other controller is running, unflushable data must be cleared from the other
controller with the CLI command, CLEAR_ERRORS controller INVALID_CACHE,
5–36.