You can create BCC load and unload scripts for each BCC-enabled resource in each peer cluster. They are used to handle the transfer of SAN devices between clusters during a failover.
Scripts written for a SAN that mirrors data between two clusters should demote/mask a LUN (or group of LUNs) for a running resource on its current cluster, swap the synchronization direction, then promote/unmask the LUN(s) for the resource on the other cluster.
You can add commands that are specific to your storage hardware. These scripts and commands might be needed to promote mirrored LUNs to primary on the cluster where the pool resource is being migrated to, or demote mirrored LUNs to secondary on the cluster where the pool resource is being migrated from.
The scripts or commands you add are stored in eDirectory. If you add commands to call outside scripts, those scripts must exist in the file system in the same location on every server in the cluster.
IMPORTANT:Scripts are not synchronized by Identity Manager.
Consider the following guidelines when creating and using scripts:
Scripts must be written in Perl or have a Perl wrapper around them.
Log files can be written to any location, but the BCC cluster resource information is logged to SYSLOG (/var/log/messages).
Error codes can be used and written to a control file so that you know why your script failed.
BCC checks only whether the script was successful. If an error is returned from the script, the resource does not load and remains in the offline state.
The BCC scripts are run from the Master_IP_Address_Resource node in the cluster.
Perl script code that you customize for your SAN can be added to a BCC-enabled cluster resource load script and unload script through the BCC management interface.
You can include parameters that are passed to each Perl script. BCC passes the parameters in the format of %parm1%, %parm2%, and so on.
There can be multiple scripts per resource, but you need to use a common file to pass information from one script to another.
The BCC load script and unload script for a BCC-enabled cluster resource must be unique on each cluster node.
To add storage management configuration information:
Log in to iManager as the BCC Administrator user.
In Roles and Tasks, click Clusters > My Clusters, then click the cluster name.
Click the Cluster Options tab.
Under Cluster Objects, select a cluster resource that is enabled for business continuity, then click Details.
Cluster resources that are enabled for business continuity have the BCC label on the resource type icon.
Click the Business Continuity tab, then click BCC Scripts.
Create BCC storage management load and unload scripts:
Under BCC Load Scripts, click New to bring up a page that lets you create a script to promote mirrored LUNs on a cluster.
You can also delete a script, edit a script by clicking Details, or change the order in which load scripts execute by clicking the Move Up and Move Down links.
Specify values for the following parameters on the Storage Management Script Details page:
Parameter |
Description |
---|---|
Name |
Specify a name for the script you are creating. |
Description |
If desired, specify a description of the script you are creating. |
CIM enabled |
Select this check box if your SAN storage system supports SMI-S. This causes the CIM-specific fields to become active on this page. It is selected by default. |
CIMOM IP or DNS |
If you selected the CIM Enabled check box, specify the IP address or DNS name that is used for SAN management. |
Namespace |
If you selected the CIM Enabled check box, accept the default namespace, or specify a different namespace for your storage system. Namespace determines which models and classes are used with your storage system. Consult the vendor documentation to determine which namespace is required for your storage system. |
User name and password |
If you selected the CIM Enabled check box, specify the user name and password that is used to connect to and manage your SAN. |
Port |
If you selected the CIM Enabled check box, accept the default port number or specify a different port number. This is the port number that CIMOM (your storage system manager) uses. Consult your storage system documentation to determine which port number you should use. |
Secure |
If you selected the CIM Enabled check box, select the Secure check box if you want storage management communication to be secure (HTTPS). Deselect the Secure check box to use non-secure communications (HTTP) for storage management communications. |
Synchronous |
Select this check box to run scripts sequentially (that is, one at a time). This is the default. Deselect this check box to allow multiple scripts to run concurrently. Most SAN storage system vendors do not support running multiple scripts concurrently. |
Script parameters |
If desired, specify variables and values for the variables that are used in the storage management script. To specify a variable, click New, then provide the variable name and value in the fields provided. Click OK to save your entries. You can specify additional variables by clicking New again and providing variable names and values. You can also edit and delete existing script parameters by clicking the applicable link. These script commands are specific to your SAN hardware. You can add Perl script commands that can be run on Linux. If you add commands to call outside scripts, those scripts must exist on every server in the cluster. |
Script parameters text box |
Use this text box to add script commands to the script you are creating. These script commands are specific to your SAN hardware. You can add Perl script commands that can be run on Linux. IMPORTANT:If you add commands to call outside scripts, those scripts must exist with the same name and path on every server in the cluster. |
Click Apply and OK on the Script Details page, then click OK on the Resource Properties page to save your script changes.
IMPORTANT:After clicking Apply and OK on the Script Details page, you are returned to the Resource Properties page (with the Business Continuity tab selected). If you do not click OK on the Resource Properties page, your script changes are not saved.