Adding Storage Arrays to Tuning Manager – Linux

— Linux based configuration —

  •  Login to the Management server as a root.


1. Navigate to Tuning manager commands location : “\opt\jp1pc\tools”.
Issue Command “./jpctminfo agtd –p” to check the version of Agent for RAID. “agtd” is the service key for RAID Agent.


Note: RAID Agent version should not be greater than the HTnM server version. Agents fails to collect data if they are higher version than HTnM server version.

  1. Each array is added to the Tuning Manager as an Instance under RAID Agent. Check for the arrays already configured on the Array.
    Issue Command “./jpcinslist agtd” – Displays all the Storage Array instances.


Adding Arrays:
3. Data collection procedures are different for USP/USPv/VSP & Thunder/AMD/HUS Arrays.
For USPv and VSP, CMD device is required which needs to be added to RAID agent instance.
For HUS, RAID Agent uses the Controller IP to communicate with the Array.

  1. For USP/USPv/VSP,
    Allocate CMD device from the storage array to the management host. Scan for the CMD device.

Make sure CMD is discovered by Tuning Manager Agent. Issue the command “./jpctdlistraid” to list the visible CMD devices on the host.


5. To add the new RAID instance, Issue Command “./jpinssetup agtd –inst VSPTEST

Choose the respective parameters
Storage Model (1:Thunder/AMS/HUS100 or 2:Lightning/USP/USP V/VSP) : 2
Command Device File Name [/dev/sda] : /dev/sdf
Unassigned Open Volume Monitoring (Y/N) [N] : N
Mainframe Volume Monitoring (Y/N) [N] : N
Store Version [2.0] :


Issue command to verify the instance added.
“./jpcinslist agtd”


  1. Start the RAID agent Instance. Issue the Command
    “./jpcstart agtd inst=VSPTEST”


7. Refresh the Storage Array Configuration. Issue Command “./jpctdrefresh -inst VSPTEST”


8. For HUS/AMS arrays, to add the RAID Instance Issue Command
./jpinssetup agtd –inst HUSTEST” and enter respective details.

Storage Model (1:Thunder/AMS/HUS100 or 2:Lightning/USP/USP V/VSP) : 1
IP Address or Host Name (Controller 0) [] :
IP Address or Host Name (Controller 1) [] :
Array Unit Name [] : HUS150_xxx
user ID [] : abids
password [] :
Re-enter :
Secure Port function? (applicable storage only) (Y/N) [N] :
Store Version [2.0] :


Repeat Step 6 & 7.

  1. Login to Tuning Manager.
    Newly added VSPTEST will not be visible in the Tuning Manager as default Data Polling schedule will be set to every 12 hours or 24 hours.


Initiate a Data Polling: Go to Administration -> Data Polling and Start polling.

  1. Storage Arrays are added to Tuning Manager once the polling completed.

3 Replies to “Adding Storage Arrays to Tuning Manager – Linux”

  1. thanks for sharing valuable information.

  2. Rick von Richter says: Reply

    These are great instructions. TYVM!

    For the newer HTnM 8.1+ versions, for new agent installs, you should probably look at using the Hybrid store. Newer installs will ask if you want to use the older Store version or the newer Hybrid version.

    Also, I see that you are selecting “N” for the Unassigned Open Volume Monitoring question.
    I have been selecting “Y” for this question because you will be missing some data stats from any pool volumes. Also, you will not be able to monitor UR Journal volumes unless you specify “Y”
    From the docs; (HCS HTnM Installation Guide HC14133, Section 8, page 8-7)
    1. If the storage system contains a pool volume, Y must be specified for
    “Unassigned Open Volume Monitoring”. If N or n is specified, the
    usage rate associated with IOs to the pool volume is not included in the
    following array group and LDEV usage rate field values:
    PI_RGS record: “Busy %” field and “Max Busy %” field
    PI_LDE, PI_LDE1, PI_LDE2, and PI_LDE3 records: “Busy %” field and “Max Busy %” field

    2. To monitor Universal Replicator journal volumes, “Y” must be specifed for “Unassigned Open Volume Monitoring”.

    1. Absolutely correct Rick. Missed that as I was trying to explain general procedure of adding arrays to Tuning Manager.

Leave a Reply