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
It is checked whether the operation is performed for the existing LDEV or not. If the operation is attempted to be performed for an LDEV that does not exist, an error is detected.
If it is not clear whether the LDEV as the target of the operation exists in the configuration definition file (if the target LDEV information does not exist in the configuration definition file), the error is not detected.
The commands as the target of the check are shown below.
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
• raidcom modify host_grp port <port#> [<host group name>] -host_mode <host mode> [--host_mode_opt <host mode option> … ]
• raidcom add hba_wwn -port <port#> [<host group name>] -hba_wwn
<WWN strings>
• raidcom delete hba_wwn port <port#> [<host group name>] -hba_wwn <WWN strings>
• raidcom set hba_wwn -port <port#>[<host group name>] -hba_wwn
<WWN strings> -wwn_nickname <WWN Nickname>
• raidcom reset hba_wwn -port <port#>[<host group name>] -hba_wwn
<WWN strings>
• raidcom add lun -port <port#> [<host group name>] {-ldev_id
<ldev#> [lun_id<lun#>] | grp_opt <group option> -device_grp_name <device group name> [<device name>]}
• raidcom delete lun -port <port#> [<host group name>] {-lun_id
<lun#> | ldev_id <ldev#> | grp_opt <group option> -device_grp_name <device group name> [<device name>]}
Check with the deletion operation
It is checked to ensure that the operation is not intended to be performed for the LDEV that is already deleted. If it is, an error is detected.
If it is not clear whether the LDEV as the target of the operation exists in the configuration definition file or not (if the target LDEV information does not exist in the configuration definition file), the error is not detected.
The command as the target of the check is shown below.
• raidcom delete ldev {-ldev_id <ldev#> | -grp_opt <group option> -device_grp_name <device group name> [<device name>]}
The example of the script where the same LDEV is attempted to be added to the already created LDEV and the execution result of the Context check is shown below.
• Example of script
• Execution result
raidcom add ldev -parity_grp_id 01-01 -ldev_id 1 -capacity 100M raidcom add ldev -parity_grp_id 01-01 -ldev_id 2 -capacity 100M raidcom add ldev -parity_grp_id 01-01 -ldev_id 3 -capacity 100M
• Example of script (the text in bold indicates the part of incorrect configuration definition.)
• Execution result (the text in bold indicates the contents of the error accompanying the invalid configuration definition in the script.)
C:\HORCM\etc>raidcom get ldev -ldev_id 1 -cnt 65280 -store ldevconf_65 >
ldevconf_65.txt
C:\HORCM\etc>raidcom zt 3_defined_ldev.bat load ldevconf_65.dat -checkmode precheck
C:\HORCM\etc>raidcom add ldev -parity_grp_id 01-01 -ldev_id 1 -capacity 100M
C:\HORCM\etc>raidcom add ldev -parity_grp_id 01-01 -ldev_id 2 -capacity 100M
C:\HORCM\etc>raidcom add ldev -parity_grp_id 01-01 -ldev_id 3 -capacity 100M
raidcom add ldev -parity_grp_id 01-01 -ldev_id 1 -capacity 100M raidcom add ldev -parity_grp_id 01-01 -ldev_id 2 -capacity 100M raidcom add ldev -parity_grp_id 01-01 -ldev_id 3 -capacity 100M raidcom add ldev -parity_grp_id 01-01 -ldev_id 1 -capacity 100M raidcom add ldev -parity_grp_id 01-01 -ldev_id 2 -capacity 100M raidcom add ldev -parity_grp_id 01-01 -ldev_id 3 -capacity 100M for /l %%i in (1,1,3) do (
raidcom add ldev -parity_grp_id 01-01 -ldev_id %%i -capacity 100M )
for /l %%i in (1,1,3) do (
raidcom add ldev -parity_grp_id 01-01 -ldev_id %%i -capacity 100M )
The number in raidcom # of raidcom_#7: [EX_CTXCHK] Context Check error is the number of times of performing the raidcom command by using
<work file>. The number of times is incremented each time the raidcom command is executed.