Appendix C. CLI
545
Draft Document for Review August 30, 2007 12:59 am
7065appCLI.fm
We will now show some specific examples of using the CLI, for tasks which have already
been demonstrated using the GUI in the main part of this book.
Add a storage subsystem to the Storage Manager configuration
Adding storage subsystems to the Storage Manager configuration can be done manually or
with an automated discovery.
1. On installation, Storage Manager has no subsystems defined. Use the option -d of SMcli
to list the defined subsystems. See “Show defined subsystems in the Storage Manager
configuration” on page 546 for a detailed description of the command shown in
Example C-2.
Example: C-2 SMcli - List storage subsystems defined in the Storage Manager configuration
amazon:/ # SMcli -d
There are currently no storage subsystems listed in the configuration file. Add
storage subsystems using the Add Storage Subsystem option in the storage
management
software or by command line.
SMcli failed.
amazon:/ #
2. To add a storage subsystem use either the option -A alone, to perform automatic
discovery of available subsystems, or specifying the controllers management interface IP
addresses, to perform manual discovery. Example C-3 shows both methods.
Example: C-3 SMcli - Add storage subsystems to the Storage Manager configuration
amazon:/ # SMcli -A 172.18.4.1 172.18.4.2
New storage subsystem was discovered at address 172.18.4.1.
-v
Only together with parameter -d. Show the health status of the defined storage
subsystems.
-e
Do not check script syntax. Optional option.
-S
Do not list progress information. Optional option.
-quick
Use this parameter to reduce the amount of time that is required to run
a single-line operation. (An example of a single-line operation is the
recreate snapshot volume command. This parameter reduces time by
not running background processes for the duration of the command.
Do not use this parameter for operations involving more than one
single-line operation. Extensive use of this command can overrun the
controller with more commands than the controller can process, which
causes operational failure. Also, status and configuration updates
normally collected from background processes will not be available to
the CLI.
This parameter causes operations that depend on background
information to fail.
Option
Description
