
2–50
HSG80 Array Controller V8.7 Command Line Interface Reference Guide
CLI Command Descriptions
Erases the entire subsystem configuration data file stored in the nonvolatile memory
(NVRAM) of “this controller.”
IMPORTANT: This command sets the controller to a default configuration and shuts down the
controller, disabling communication between host and controller. Enter new configuration
information through the SET THIS_CONTROLLER command or the CONFIGURATION
RESTORE command to make the controller operational.
This command does not erase the configuration file that was stored on disk with the
INITIALIZE container-name SAVE_CONFIGURATION command.
NOTE: Before issuing this command, make sure the subsystem configuration is saved.
•
In single-controller subsystems, the configuration is saved on the disk array. If a container
has the SAVE_CONFIGURATION switch specified when it is initialized (through the
INITIALIZE command), the disks that constitute that unit is able to save a copy of the
configuration.
•
For dual-redundant controllers, the configuration is stored in the companion controller.
Specify the CONFIGURATION RESET command on “this controller” in nofailover
mode (SET NOFAILOVER or SET NOMULTIBUS FAILOVER CLI command) only.
Enter this command to ensure all of the old configuration information is removed
when a controller module is moved from one subsystem to another.
Dual-redundant controller subsystems have the configuration information stored on
the “other” controller and do not need to use the INITIALIZE container-name
SAVE_CONFIGURATION command unless the subsystem is being upgraded (for
example, both controllers are being replaced with newer versions).
•
New subsystem configuration information can be re-entered by using the SET
THIS_CONTROLLER command.
•
Saved subsystem configuration information can be re-established by using the
CONFIGURATION RESTORE command.
•
New subsystem configuration information can be re-established by using the SET
FAILOVER COPY or SET NOMULTIBUS FAILOVER= command. These CLI
commands “copy” the configuration file from the defined controller nonvolatile
memory and place the file into the redundant controller nonvolatile memory. For
example, use SET FAILOVER COPY=OTHER_CONTROLLER or SET
NOMULTIBUS FAILOVER executed from “this controller” to place the “other
controller” configuration file into the “this controller” nonvolatile memory.
•
Ensure subsystem configuration is stored on disk for single controller subsystems
by way of the INITIALIZE container-name SAVE_CONFIGURATION or the
CONFIGURATION SAVE command.
CONFIGURATION RESET