HP EVA Performance Management Pack v3

This management pack is based on HP EVA Performance Management Pack v2 by Alain Côté. Some improvements that I’ve made in v3:

  • Scripts are composed in a shared data sources to support ‘cookdown’
  • New classes for better targeting and granularity
  • Most of the collection rules have a short knowledge articles
  • Added the Unit Monitor that checks for friendly names config file existence and generates an alert (including a knowledge base article)
  • Minor scripts improvements. New scripts a little bit more stable and should not fail if you do not have an optional components (like a data replication groups) on your EVA
  • New views
  • Collection Rules for Windows PerfMon Counters are added (this rules are disabled by default)
  •  Diagnostic task for Disk Group – Average Write Latency Monitor shows a TOP 5 virtual disks for Write Latency (not for activity, we’re found that top 5 active (in+out MB\s) disks don’t help us to  troubleshoot, just because our biggest virtual disks are always on top, not the slowest disks which are the ‘latency generators’)
  • New reports (defined in the dedicated management pack)

 

UPDATED (ver. 3.0.0.226 for unsealed and 3.0.0.225 for the sealed one):

  • Fixed the bug in the EVA.Disk.Group.Write.Latency.Monitor

UPDATED(ver. 3.0.0.224):

  • Increased discovery timeouts
  • Fixed typos in discovery scripts

UPDATED

 

(ver. 3.0.0.222):

  • Fixed typo in diagnostic scripts
  • Changed the Event Source for the event that diagnostic task create

53 thoughts on “HP EVA Performance Management Pack v3

  1. David

    I was able to get the Hp EVA Management Pack working somewhat, so far I have not received data from EVA Host Port and EVA Virtual Disks, I barely have 3 hours since I set up the MP thus I will just wait till tomorrow just to see if discovery is able to find these objects. As far for finding the EVAs and Disk Groups, it found all of them and showing great performance data.

    On another note, when I tried to install the EVA Reporting Package its failing with dependencies on the EVA Management Pack 3.0.0.203, I was able to change it to 3.0.0.208, but still got issues on it. Not a big issue though as I am mainly concern for the EVA Management Pack fully working.

    Well I will let you know if the MP discovers the Host Ports and Virtual Disks by tomorrow.

    Thanks,
    David

  2. Alexey Zhuravlev Post author

    Hi David,

    >but still got issues on it.
    It looks like you trying to import a two unsealed versions. It’s impossible. You can not refer to unsealed MP from another MP, that’s why you can not import the reports.
    Unsealed versions was included in the archive as the source codes for a users who want to change this MP. It was not intended for import ‘as is’ (unsealed).

  3. David

    Thanks Alexey, well as an update all devices did show up, have lots of good data on this MP, still working on some issues, does not look like this MP is that intensive on my SMA.

    -David

  4. David

    The MP as a whole, from processes point of view, usage of memory, usage of processor %, network performance from SMA is not resource intensive to my server. The default querying time for the monitors/rules are good.

    Thanks,
    David

  5. Rasmus H C

    Thank you a lot for the MP, it is really nice and easy to use. It is really a good job you guys made!!!!

    I have a few requests for changes / extra functionality :
    • It could be nice if it is possible to store the temp files in system variables %temp% instead of C:\temp
    • Is it possible to collect % usage of each Vdisk and each Disk group (that could be used for trending)
    • Is it possible to collect the temperature of the EVA?
    • It could be nice to have Alert View in the MP that shows all active EVA alerts.

  6. iMav

    Hi,

    Great MP but getting these errors:

    Data was found in the output, but has been dropped because the Event Policy for the process started at 4:33:00 PM has detected errors. The ‘ExitCode’ policy expression:
    [^0]+
    matched the following output:
    3

    Command executed: "C:\Windows\system32\cscript.exe" /nologo "EVA_Virtual_Disk_Performance_Provider.vbs"

    AND

    Forced to terminate the following process started at 4:29:00 PM because it ran past the configured timeout 60 seconds.

    Command executed: "C:\Windows\system32\cscript.exe" /nologo "EVA_Virtual_Disk_Performance_Provider.vbs"

  7. Alexey Zhuravlev Post author

    Check your c:\temp folder: LocalSystem (or another account if you’re using a custom account as a service account) must have a full rights. Do you see a files in c:\temp like *EVA*.txt ? How many vDisks you have?

  8. iMav

    I’ve granted localsystem and my action account full rights.

    Already got the .csv files in c:\temp

    Got a total of 124 vDisks over 2 SAN

    Will check if thing go right now

  9. iMav

    Still getting the time out errors 21402

    Forced to terminate the following process started at 9:19:00 AM because it ran past the configured timeout 60 seconds.

    Is it possible to adjust the timeout settings to let’s say 120 sec?

  10. iMav

    Works like a charm! Thanks.

    Just one issue left, the reports are throwing me an error.

    Query execution failed for dataset ‘GroupProperties’

  11. The Borg

    There is an error in the vDisk and host port discoveries:

    WshShell.Run(strcommand),,True is not valid

    Edit and replace with :
    WshShell.Run strcommand,,True

    Then you will need to re-seal and re-import to get working.
    other than that, a brilliant MP.

    -_Andrew
    :

  12. Vgkda

    In my case, the vDisk and host port were discovered with the strange names but when I’ve applied the solution to get friendly names, they disapeared from the monitoring view.

    The fnamehosts.conf is generated and contains the friendly names, which appear for the EVA and EVA Disk Group.
    But not for vDisk and host ports which are apparently not anymore monitored
    Regards

  13. gsollis

    Thanks for fixing the faults, seems to have worked great 🙂 I assume the discovery of the Virtual Disks and Host Ports can also take a day or two? I currently see no counters of these yet, I installed about 3 hours ago. This is the first time with this MP.

  14. TheGord

    Apologies for the basic questions but I think i’m missing steps.
    Once the management pack is imported, should it automatically find any and all Command View/EVA Per servers? Then by extention the EVAs themselves?
    In the Discoveries section of the doc, it’s mentioned that the EVAPERF Discovery is disabled by default. Does that need to be enabled before anything will show in the management pack?
    Also, regarding credentials, does the service account for SCOM need specific rights within the HP utils, CV, EVAPerf, SMI-S, etc?

    Thanks

    G.

  15. Alexey Zhuravlev Post author

    >Does that need to be enabled before anything will show in the management pack?
    Yes, it does.

    >Also, regarding credentials, does the service account for SCOM need specific rights within the HP utils, CV, EVAPerf, SMI-S, etc?
    You need an access to evaperf only.

  16. TheGord

    Thanks for your reply.

    So when you say to enable via override, this is supposed to be done via ‘authoring’, ‘rules’, or ‘monitors’?
    I don’t see the highlighed name or target in there.

    Thanks for your assistance.

    G.

  17. Olaf

    Hi, great work, this is really a usefull MP for us.
    I have a question about deleted vdisks. How do i get rid of deleted vdisks? Is there any process which deletes orphaned objects?

    regards, Olaf

  18. Olaf

    Hmm, we have a lot of vDisks entities without the friedly name, because for a short time the MP was running without a valid friendly names config file. These entries are rather old, and unfortunately they don’t disapear automatically.
    Does anyone know how we can get rid of these old entries?

    regards, Olaf

  19. Sidorenko Andrey

    Alexey, thank you for MP.
    But, i have some problems with installation and usage.
    1. I Cant install unsealed MPs. If i try to install unseal HP EVA Management Pack after i can`t install any of reports MP (sealed or unsealed). Reports MP say that i doesn’t have HP Eva Management Pack
    2. On my EVA (6400) i have 2 controllers and 2 Disk Groups, but in EVA Disk Groups – State i see 4 Groups (Controller1 – Group1, Controller1 – Group2 and same on Controller2). How can Fix this, and see only 2 Disk Groups ?
    3. After Enabling EVA Discovery on Command View server i begin receive a VBS Scripts Errors: EVA_Disk_Group_Perf_Provider.vbs(80, 1) Microsoft VBScript runtime error: Invalid procedure call or argument and EVAPerf_Total_MBs.vbs(48, 1) Microsoft VBScript runtime error: Invalid procedure call or argument
    4. In Monitoring View i doesn’t see status of any EVA Host Port All ports a not monitored.
    Please answer how i can fix this bugs.
    My Systems : RMS
    Windows 2008 R2 SP1
    SCOM 2007 R2CU4
    EVA Command View System
    EVA 6400
    Microsoft Windows 2008 R2 SP1
    EVA Command View 9.3
    EvaPerf 9.3.0.072800A

  20. Alexey Zhuravlev Post author

    1. You could use the Reports MP only with the sealed version of the ‘main’ MP. It’s by design, because you can’t refer to unsealed MP.
    2. It’s by design. The only way to ‘fix’ this is create your own discovery
    3. I can’t say for sure what causes this errors. You need to investigate further. Check a temp files (in a c:\temp directory). Try to run this scripts manually.
    4. Again, it’s by design. Read the MP Guide. Ther is no monitors targeted to HostPorts.

  21. Sidorenko Andrey

    Alexey, thank you for reply.
    I have a question about default values of different monitors.
    For Example: By defaults 2 ms of AverageWriteLatency it’s critical rate and system generate alerts.
    Maybe you can tell in which docs you find default values for you MP?
    Thank you.

  22. MJ

    Hi Alexey,
    Thanks for the work you have done so far and thanks for this update. This will help stop the script from timing out on our servers. In our enterprise environment, we are getting Disk Write Latency spikes over 20ms all the time, but this is considered stable in our environment. Is there any way to include a "Samples" override as well as a "Treshold" so we can rule out these spikes from the alert monitor?

  23. Alexey Zhuravlev Post author

    Sorry for the delay…

    Hello kcnb,

    This MP was tested on a Windows Server 2008 R2. Actually, my test and prod servers are Windows Server 2008 R2.

    Hi MJ,

    Good question. There is no way to do it with the _current_ version (because you’ll need to rewrite all monitors to achieve that). But it’s a good DCR. Thanks.

  24. Eric Meloche

    Hi Alexey,

    Thanks for writing this one!
    I have 2 servers where evaperf is installed and they are installed on a Windows server 2003. Will it work?
    if not, should i only installed an instance of evaperf on a dedicated Windows 2008 R2 Server?

    regards,

  25. Alexey Zhuravlev Post author

    Hi Eric,

    I had problems with this MP running the evaperf on Windows Server 2003 machines. All perf collections suddenly stops. So I never recommend to use a Windows Server 2003 machines. In short- it will work but could be unpredictable and unstable from my expirience.

  26. Eric Meloche

    Thanks Alex,

    This is exactly the symtpom we have. It started with the V2 version.
    Willstart thinking to move on a 2008 R2 server
    Which version of command view should we used?

    Eric

  27. Eric Meloche

    Thanks Alex,

    This is exactly the symtpom we have. It started with the V2 version.
    Willstart thinking to move on a 2008 R2 server
    Which version of command view should we used?

    Eric

  28. Hans Gustafsson

    Hi, I have problem checking EVA Total MB/s for one of our systems,

    when compering the EVAPerf_Total_MBs.vbs and EVAPerf_Total_Reqs.vbs, only EVAPerf_Total_MBs.vbs has the line Name = “”  may that be the problem that it doesn’t work as expected? EVA Total Req is working as it should.

    Regards
    Hansel

  29. Miguel Angel Vega Hirata

    Thanks for  making this management pack.

    I was trying to find a mp that didn’t rely on the hp webes software for monitoring.

    Hp storage management pack relies on webes only for the eva monitoring. Trouble comes when hp retired support  for the insight remote support tools 5.8  . The next version of hp insight remote support tools runs only in windows 2008. Our customer has legacy infrastructure running 2003 servers and no plans to upgrade  , so your mp seems like a life saver to keep eva monitored from scom .

     

  30. Miguel Angel Vega Hirata

    Thanks for  making this management pack.

    I was trying to find a mp that didn’t rely on the hp webes software for monitoring.

    Hp storage management pack relies on webes only for the eva monitoring. Trouble comes when hp retired support  for the insight remote support tools 5.8  . The next version of hp insight remote support tools runs only in windows 2008. Our customer has legacy infrastructure running 2003 servers and no plans to upgrade  , so your mp seems like a life saver to keep eva monitored from scom .

    Thanks a lot

  31. Alexey Zhuravlev Post author

    Thank you.

    Actually, this MP is not a replacement for the vendor MP. HP management pack is about health alerts (delivered via webs). The MP posted here is all about performance. No alerts on EVA component(s) failures etc.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.