Block Storage

 Export Tool(Monitor2)

Jump to  Best Answer
Sudhir BISHT's profile image
Sudhir BISHT posted 09-13-2025 13:26

Hi All. I want to understand how this tool works.   Hitachi Export Tool (monitor2)

I ran it and it seems to run fine:

[root@xxxxxxxxx 93-07-24]# sh ./runUnix.sh show interval -ip 10.X.1.XX -login user pass
Interval : 5 min
show interval command success

Now, how this will run again as I ran it manually once. Do we need to put in crontab etc.  It runs manually okay once, but how it will continuously collect perf data.

And, also we have a server from where it can run fine manually.  But we want that data into another server (from this another server we can't run export tool as it can't connect to Controller IP). But this server has our tool which needs Export Tool data for performance. So, can we mount the FS where it runs fine into this server and then get the Perf data.  Is that possible. 

README of the Tools says this:

3. Installation on the UNIX System
 < Installation >
  Install the new version of Export Tool 2 by following the installation
  procedure below.
 (1) Login with SuperUser.
 (2) Mount the CD-ROM.
 (3) Create a directory(ex. /monitor).
        # mkdir /monitor
 (4) Change the directory to the directory which is created (3).
        # cd /monitor
 (5) Input the command follows,
        # cp -r /(CD-ROM MountPoint)/program/monitor2 .
 (6) Change the directory to the directory which is /monitor/monitor2.
        # cd /monitor/monitor2
 (7) Give an execution authority for runUnix.sh
        # chmod a+x runUnix.sh
Thats it , it says. They don't even don't mention the command which I ran above.  Anyway, the thing is how this will run continuously. How to setup that.  Plus the other query above.

Please advise.

Thanks.

Andrew Romero's profile image
Andrew Romero posted 09-13-2025 22:12  Best Answer
Hi
 
Below are my draft Export Tool (v2) notes
 
** These discuss the default directory for output and logs
 
Andy R.
 
#####################################################
Export Tool(v2) notes
#####################################################
 
[] Install modern Java run-time for your OS
 
[] Make sure the full-path to java.exe is in the PATH
 
[] Screen buffer height 1500
 
 
[] Create a tool tree to store the tool
 
   My (Windows) tree looks like this:
 
    C:\sannas\hdsperf
 
    # For e-series    
    C:\sannas\hdsperf\E-series
    C:\sannas\hdsperf\E-series\monitor2
 
    # For F/G series
    C:\sannas\hdsperf\fg
    C:\sannas\hdsperf\fg\monitor2
 
    I see no reason why this tool tree couldn't be 
    based on a Windows network share UNC path
    ( \\myserver\hdsperf instead of C:\sannas\hdsperf )
    or on a Linux path corresponding to an NFS volume.
 
 
 
[] Download the Document & Programs CD ISO from the Hitachi Vantara Support web-site
 
   The export tool v2 is in this sub-directory in the ISO:  \Tools_Pack\monitor2
 
   NOTES:
     - I believe that the version of the ISO that you download should be
       the one that corresponds to the firmware version on your array.
       I'm pretty sure that a new ISO is *NOT* released with each array fw release.
       So the correct ISO may be slightly older than your array's fw. 
       (Hitachi subject matter experts chime in )
 
     - I believe that the monitor2 tool files for each array type ( F/G, E, VSP-One)
       are slightly different, so If you have multiple array types, you probabably need
       to download the correct ISO for each type. (Hitachi subject matter experts chime in )
 
 
[] Copy the files and sub-directories
   
   FROM: The correct ISO:   \Tools_Pack\monitor2 sub-directory
   TO:   The correct monitor2 sub-directory in your tool tree
 
 
[] Create the log and out sub-directories in the monitor2 sub-dirs of
   your tool tree
 
    In my case:
    
    C:\sannas\hdsperf\E-series\monitor2\log
    C:\sannas\hdsperf\E-series\monitor2\out
 
    C:\sannas\hdsperf\fg\monitor2\log
    C:\sannas\hdsperf\fg\monitor2\out
 
   When you run the tool to acquire performance data, output is written to 
   the "out" sub-directory
 
   And, as expected log info is written to the "log" sub-directory
 
[] Run the tool to acquire some performance data
 
   Simple Examples:
 
   runWin.bat export data -ip arrayCtlIP -range 202508061400:202508061500 -group PortError -option nocompress clear
 
   runWin.bat export data -ip arrayCtlIP -range 202508061400:202508061500 -group Port -option nocompress clear
 
   # for VSP-one block arrayCtlIP should probably be the ESM IP ( experts ..chime in )
 
 
   NOTES: IF you run mutiple instances, make sure to use separate output dirs and start jobs a couple minutes apart
          I beleive that the runWin / runUnix shell scripts allow you to specify a different output directory using
          this parameter:  -outpath <output-directory>
 
 
 
[] Official usage Doc is here
 
   https://docs.hitachivantara.com/r/en-us/virtual-storage-platform-one-block/a3-04-0x/mk-23vsp1b004/about-export-tool-2

Andrew Romero's profile image
Andrew Romero posted 09-13-2025 19:09
Hi
 
 
In a quest to implement some simple performance monitoring,
I started experimenting with the export tool ( v2 ) also.
 
I'm using Windows for my tests.
 
I noticed that extracting data just for one perf group, for a 1 hour time range takes about 10 mins.
 
sample command:
 
runWin.bat export data -ip ArrayIP -range 202508061400:202508061500 -group PortError -option nocompress clear
 
I'm sure you can run the tool using Linux cron or Windows Task Scheduler.
 
You will likey want to start with:
  - only one group
  - specify a time range slightly less than 24 hours
    ( the array holds 24 hours of data ... I think ?? experts correct me )
    ( coordinate the start time of your scheduled task with the range
      specified so as not to request data that was no longer available)
  - watch how long it takes to run. Add more groups
 
Then view / analyze your data. I'm planning on initially using Python and Pandas and Matplotlib in a Jupyter notebook.
 
 
 
Experts ... please chime in
 
Andy
 
Sudhir BISHT's profile image
Sudhir BISHT posted 09-13-2025 20:17

Hi Andrew.  Thanks.

Good to know that there is an export switch in it as well.  Readme just says to run it but then what. Where it sends that data.

We do have a tool STOR2RRD, and there the same export tool is run with just:

bash runUnix.sh show interval -ip 10.X.1.XX -login maintenance <password>

And they have some intelligence in-built in the tool that it collects all data and shows in graphs/metrics. Probably internally exports it as well as they use perl.

However, in my current scenario, I want to do it myself for another tool. And, that tool doesn't have access to VSP Controllers so can't run it there. So, want somehow to run it on a server which has access to controllers (that server is Ops Analyzer) and then export it to the server which has the monitoring tool's datacollector installed.  

On Ops Analyzer it runs perfectly. I want somehow to get what it collected into another server and just point it to that. Possible.

Thanks