6.5 HP StoreAll OS CLI Reference Guide

1. Add-on Scripts names should be in the defined format. This should be strictly followed as
<release Number>_<add-on_script_name>.sh.
When you provide the version number, remove the period between the first and second digit
of the version number.
[root@host2 /]# ibrix_version -l
Fusion Manager version: 6.3.33
==============================
Segment Servers
===============
HOST_NAME FILE_SYSTEM IAD/IAS IAD/FS OS KERNEL_VERSION ARCH
–------—- --------------------------------- ------- ------ ---------
-------------- ----
host2 6.3.33(internal rev 132818 in SVN) 6.3.33 6.3.33 GNU/Linux
2.6.18-194.el5 x86_64
In this example, the version displayed is 6.3.33. Use the first two digit of the version number,
6.3 for example, as a prefix to “Add-on Script File Name” without “.” (Dot), so that the name
of an add-on script named AddOnTest.sh would be 63_AddOnTest.sh.
IMPORTANT: The version provided in the name must match the version of StoreAll on which
you plan to run the script. For example, any add-on script that you want to run on StoreAll
version 6.3, must have 63_ in its file name; otherwise, the script will not run. For example, if
you prefix the name with another version, such as 62_, and you attempt to run the add-on
script on StoreAll 6.3, the script will not run.
2. Place the added-on script in the following directory:
/usr/local/ibrix/ibrixcollect/ibrix_collect_add_on_scripts/
The following example shows several add-on scripts stored in the
ibrix_collect_add_on_scripts directory:
root@host2 /]# ls -l
/usr/local/ibrix/ibrixcollect/ibrix_collect_add_on_scripts/
total 8
-rwxr-xr-x 1 root root 93 Dec 7 13:39 60_addOn.sh
-rwxrwxrwx 1 root root 48 Dec 20 09:22 63_AddOnTest.sh
3. Write an add-on shell script that contains a custom command/log that needs to be collected
in the final StoreAll collection. Only StoreAll and operating system commands are supported
in the scripts. These scripts should have appropriate permission to be executed.
IMPORTANT: Make sure the scripts that you are creating do not collect information or logs
that are already collected as part of the ibrix_collect command.
4. Make sure that add-on scripts that collect the custom logs redirects the collected custom logs
to the directory local/ibrixcollect/ibrix_collect_additional_data. Only files
copied to this location will be included in the generated IbrixCollect tar file. Output of the
add-on scripts is available only when the IbrixCollect process is completed and the tar files
containing the output are extracted. See “Running an add-on script” (page 45) and then
“Viewing the output from an add-on script” (page 46).
Running an add-on script
To run an add-on script:
ibrix_collect 45