CLI Guide

Table 20. controllers properties (continued)
Name Type Description
● Yes: The partner controller has either failed or been shut down, and its
responsibilities have been taken over by this controller.
There will be a delay between the time that the value of the status property
becomes Down for one controller and the time that the value of the failed-
over property becomes Yes for the other controller. This time period is the
time that it takes for a controller to take over the responsibilities of its partner.
failed-over-numeric uint32 Numeric equivalents for failed-over values.
● 0: No
● 1: Yes
fail-over-reason string If failed-over is Yes, a reason for the failover appears; otherwise, Not
applicable appears.
fail-over-reason-numeric uint32 Numeric equivalents for fail-over-reason values.
sc-fw string Storage Controller firmware version.
vendor string Controller manufacturer.
model string Controller model.
platform-type string Enclosure platform type.
platform-type-numeric uint32 Numeric equivalents for platform-type values.
multicore string Shows whether the controller module is using multiple application processing
cores.
● Enabled: Multiple cores are active.
● Disabled: A single core is active.
multicore-numeric uint32 Numeric equivalents for multicore values.
● 0: Enabled
● 1: Disabled
sc-cpu-type string Storage Controller processor type.
sc-cpu-speed sint32 Storage Controller processor speed.
internal-serial-number string Internal serial number of the controller.
cache-lock string Shows whether hosts are prevented from using the SCSI MODE SELECT
command to change the write-back cache setting of the storage system.
● No: Hosts are permitted to disable write-back cache.
● Yes: Hosts are prevented from disabling write-back cache.
cache-lock-numeric uint32 Numeric equivalents for cache-lock values.
● 0: No
● 1: Yes
write-policy string The current, system-wide cache policy as determined by auto-write-through
(AWT) logic. This value is not settable by users. If an AWT trigger condition
(such as a CompactFlash failure) is met, the cache policy for all volumes changes
to write-through, overriding the volume-specific settings. When the problem is
corrected, the cache policy reverts to the value configured for each individual
volume.
● write-back: This is the normal state.
● write-through
● Not up: The controller is not up.
write-policy-numeric uint32 Numeric equivalents for write-policy values.
● 0: write-back
● 1: write-through
302 API basetype properties