HP Storage Arrays Space Collector CLI (HPSASC) was created with one simple idea – to collect and store capacity for EVA storage array(s). Optionally, capacity from RAID 600 (also known as XP20000/XP24000) can be collected as well.
HP Storage Arrays Space Collector CLI requires .Net Framework verion 3.5 (or higher) installed on the computer and Microsoft Access 2010 Runtime.
The tool is consists of the following components:
How to use?
There is no installation process, so you only have to copy all files in a folder with read/write access.
After that some modifications in the sample XML config file are needed.
The XML config file is divided into three sections. The first two sections are for the storage arrays and the third is the email (see screenshot below)
If you need to add additional EVA or XP storage array record, simply multiply the tags. Important – do not misplace inner tags position.
From the inner tags the most important is “xxxCFGPath” – “EVACFGPath” and “XPCFGPath”. This tag specifies where to look for and which one is the config file. The difference here is that for the EVA storage arrays, HPSASC is expecting XML file created by HP Configuration Collector tool (available for download from www.evasanstorage.com or www.hp.com). For the XP storage arrays, HPSASC is looking for one very specific file - LdevCapaCount.txt. Normally, the default path where this file is stored on SVP is at the DKC200/config folder.
If you do not want to collect capacity for XP array(s), you can remove all <XP></XP> tags closed between <XPs></XPs>.
In case HPSASC is not able to reach/read from the file, the following error will be displayed:
Parsing EVA config file: EVA02.xml
*** ERROR *** Storage Array Space Collector cannot access data for EVA EVA2.
*** ERROR *** Please check the following file and if it is accessible – EVA02.xml
The last section defines mail behavior. It is enclosed between <MailData> and </MailData> tags.
The first inner tag specifies whether the mail have to be send to predefined recipients at <To> and <Cc> tags. With this version SMTP authentication is not supported.
Every time when HPSASC is being executed, data is stored into the Access database. There can be only one record stored per day for array. If there is already record stored in the database for the current date and array, the record is deleted and new data record is created. Important requirement in this version is that date (short) format have to be in the following format – dd/mm/yyyy. This behavior will be fixed in the next release.
Note: At present, GUI editor is currently developed which will allow easy modifications of this XML config file.