Hitachi HUS VM, Руководство пользователя и справочник

Страница: 105 / 530

The script is executed only when no error is detected by the checking of
whole script contents.
The following resources can be the target of the check:
• LDEV
• Port
• Host group
Checking the contents before executing the script helps reduce debugging
after running the script.
How to check
The script is performed by specifying it as follows.
raidcom -zt <created script file name>
raidcom -zt <created script file name> -load <configuration file>
raidcom -zt <created script file name> -checkmode precheck
raidcom -zt <created script file name> -load <configuration file> -checkmode precheck
Details of check contents
Details of Context check is described below. checking contents before issuing
a script can reduce load for the debug operation in a way of executing script.
LDEV check
The check is performed from the following perspective. Note that checking for
the object information that is related to the LDEV such as pool or device
group, or an attribute of LDEV is not executed.
Check with the additional operation
It is checked to ensure no same LDEV as the already existing LDEV is added.
If the same LDEV is attempted to be added, an error is detected.
If it is not clear whether the LDEV to be added exists or not (if the target
LDEV information does not exist in the configuration definition file), the error
is not detected. Therefore, the script is executed and the LDEV is added.
The command as the target of the check is shown below.
raidcom add ldev {-parity_grp_id <gno-sgno>| -external_grp_id
<gno-sgno> | -pool {<pool ID#> | <pool naming> | snap}}
{-ldev_id <ldev#> | -tse_ldev_id <ldev#>} {-capacity <size>
| -offset_capacity <size> | -cylinder <size>} [-emulation
<emulation type>][-location <lba>][-mp_blade_id <mp#>]
[-clpr <clpr#>]
Check with the attribute setting
CCI functions
3-27
Command Control Interface User and Reference Guide