Take the following procedures to register the iSCSI disk in a class in the environment of GDS 4.3A30.
Information
When OS is started, if it takes much time until the OS recognizes the iSCSI device, the startup of GDS will be suspended until the OS recognizes the iSCSI device. This can avoid the trouble that the GDS class is not started.
The following setting is also recommended for the system where the iSCSI disk is already registered in the class. This setting changes the GDS operation only when it takes much time until the OS recognizes the iSCSI device. In other cases, GDS operation is not changed by this setting.
Apply the following patch.
For the cluster system, apply the patch on all nodes.
Version | OS | Package | Patch No. |
4.3A30 | RHEL6(Intel64) | FJSVsdx-bas | T009987LP-01 or later |
4.3A30 | RHEL6(x86) | FJSVsdx-bas | T013020LP-01 or later |
Add the setting of the SDX_ISCSI_DISK parameter to the /etc/opt/FJSVsdx/sdx.c file.
For the cluster system, apply the setting on all nodes.
[Before change]
#ident "@(#).sdx.cf 41.1 02/06/05 TDM" # SDX_DB_FAIL_NUM=0 ...
[After change]
#ident "@(#).sdx.cf 41.1 02/06/05 TDM" # SDX_DB_FAIL_NUM=0 ... SDX_ISCSI_DISK=1 <= Add this entry
Restart the system.
For the cluster system, restart all nodes.
If the iSCSI disk is already registered in a class, start the system in multi-user mode, and then execute the following command.
For the cluster system, execute the command on all nodes.
# /etc/opt/FJSVsdx/bin/sdxiscsi -S
The sdxiscsi command adds the iSCSI device that is registered in a class to the iSCSI device list of GDS.
Note
Execute the following command with the superuser authority.
A disk in SWAP state cannot be added to the iSCSI device list. Restore the SWAP disk first and then execute the command.
Do not execute other GDS commands when this command is executed.