HP MSA2000 Monitoring Management Pack

HP MSA2000 Monitoring Management Pack (MSA :: 1.0.0.0)

Most of the rules, monitors and discoveries have a Knowledge Articles.
First actions:

1. Download and install HP P2000 MSA Monitoring Tool (ftp://ftp.hp.com/pub/softlib2/software1/sc-windows/p1993940870/v70415/cp015535.exe) on monitoring hosts.
2. Provide Credentials
3. Discover HP MSA2000 System.

One agent can manage only one HP MSA2000 Modular Smart Array.

Custom MSA P2000 Management Pack (Custom.MSA.P2000 :: 1.1.3.8)

How to deploy this MP

1. Log on to SCOM Agent Server which will gather XML files
2. Under HKLM insert registry key: SOFTWARE\Wow6432Node\Hewlett-Packard\MonitorMSAP2000isInstalled
3. WARNING: Modifying REGISTRY settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of REGISTRY settings can be solved. Modifications of these settings are at your own risk.Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs.
4. Preparing Agent to Collect XML Data from SCOM:

• Download HP P2000 MSA Performance Tool from Here
• Copy downloaded files on Server:

libiconv-2_.dll
libxml2-2_.dll
libz_.dll
msacli.exe

• In folder where MSA Tool was installed create XML file with name: get_astat.xml and put following code into it:

<msacommandlist>
<command>show system</command>
<command>show host-port-statistics</command>
<command>show controller-statistics</command>
<command>show vdisk-statistics</command>
<command>show volume-statistics</command>
<command>show disk-statistics</command>
</msacommandlist>

• Create Batch File for each MSA Storage

C:\SCOM_Perf\msacli\msacli.exe” -ip 10.15.16.17 -user monitor -pass pwd -cmdfile “C:\SCOM_Perf\msacli\get_astat.xml” -outdir “C:\perf\MSAfriendlyName1” -format xml:verbose -noConsole -fwVersion false -errFileName staterrormsg.txt
Exit

• Save Batch files under: C:\SCOM_Perf\msacli\CMDScripts Folder
• Prepopulate folders for each MSA Storage. For example if you have three storage systems create folder structure:

C:\perf\MSAfriendlyName1
C:\perf\MSAfriendlyName2
C:\perf\MSAfriendlyName3

• Create Another Batch file which will Call above mentioned Batch file-s with a name: get_HP-P2000_G3.cmd and save it in folder with other scripts. For example:

start C:\SCOM_Perf\msacli\CMDScripts\MSAfriendlyName1.cmd
start C:\SCOM_Perf\msacli\CMDScripts\MSAfriendlyName2.cmd
start C:\SCOM_Perf\msacli\CMDScripts\MSAfriendlyName3.cmd

• Create a Schedule task which will call get_HP-P2000_G3.cmd script every 2 minutes. You can also run this in elevated mode and task will be created:

schtasks /create /tn GET_P2000_SCOM /tr “C:\SCOM_Perf\msacli\CMDScripts\get_HP-P2000_G3.cmd” /sc minute /mo 2 /ru SCH.MSAdataForSCOM /rp SetComplexP@$$word!!!

5. Once script starts to gather XML files we can proceed with standard Management Pack Import.

This is it. After a while data should Visible in SCOM..

Still not working? Check these notes:

Note1: You can also create just one Batch script and run it in a Schedule. But we decided to separate them se we do not have to rebuild schedule task each time new MSA Storage arrives.

NOTE2: This is where SCOM will look for data. If folder already exists it should be renamed. Data for each MSA instance must be saved in separate folder under C:\Perf

 For Example:

C:\Perf\MSAfriendlyName1
show__controller_statistics.xml
show__disk_statistics.xml
show__host_port_statistics.xml
show__system.xml
show__vdisk_statistics.xml
show__volume_statistics.xml

C:\Perf\MSAfriendlyName2
show__controller_statistics.xml
show__disk_statistics.xml
show__host_port_statistics.xml
show__system.xml
show__vdisk_statistics.xml
show__volume_statistics.xml

NOTE3: If you are having problems you might want to check: if msacli.exe, get_astat.xml and Batch Scripts are correctly called by Task or other CMDs.