User`s guide

SET OTHER_CONTROLLER
When first installed, the controller’s terminal parity is set to
NOTERMINAL_PARITY.
TERMINAL_SPEED= baud_rate
Sets the terminal speed to 300, 600, 1200, 2400, 4800, 9600 or 19200 baud. The
transmit speed is always equal to the receive speed.
When first installed, the controller’s terminal speed is set to 9600 baud.
TMSCP_ALLOCATION_CLASS= n
Specifies the allocation class (0–255 in a single controller configuration or 1–255
in a dual-redundant configuration).
When first installed, the controller’s TMSCP_ALLOCATION_CLASS is set to 0.
Qualifiers for HSZ Controllers
CACHE_FLUSH_TIMER= n
CACHE_FLUSH_TIMER=DEFAULT
Specifies how many seconds (1–65535) of idle time may elapse before the write-
back cache flushes its entire contents to disk. After the specified time, the
write-back cache flushes its contents to disk to ensure data integrity.
CACHE_POLICY=A (Default)
CACHE_POLICY=B
Allows selection of the write-back cache battery policy used by the controller.
The policy affects the availability of RAIDsets and mirrorsets when the battery
condition is low during controller intialization.
Changing this policy on one controller in a dual-redundant controller
configuration automatically changes it on the other controller. The parameter
change takes effect immediately.
The CACHE_POLICY setting affects RAIDsets and mirrorsets as follows:
• If the CACHE_POLICY on the controller is set to A and the batteries are low
when the controller initializes, any RAIDset or mirrorset that does not have
access to good batteries is made inoperative.
• If the CACHE_POLICY on the controller is set to B and the batteries are low
when the controller initializes, any RAIDset or mirrorset that does not have
access to good batteries is accessed in write-through (read cache) mode.
Regardless of the CACHE_POLICY setting, a low or bad battery affects controller
operation:
• Stripesets and disk-based units with write-back caching enabled are accessed
in write-through (read cache) mode, as long as unwritten cache data has not
been lost.
• HSJ- and HSD-based RAIDsets and mirrorsets fail over to the companion
cache in a dual-redundant configuration, provided the other cache’s batteries
are fully charged. RAIDsets and mirrorsets on HSZ and nonredundant
controller systems will not fail over.
If the batteries go low after controller initialization, unwritten cache data
is flushed from the cache and any RAIDset or mirrorset that does not have
access to good batteries is made inoperative, regardless of the cache policy.
• If the batteries are bad or missing, RAIDsets and mirrorsets are made
inoperative.
B–70 Command Line Interpreter