HP Storage Management Pack Updated to Version 3.0 – Review


HP has released the 3rd version of their management pack for monitoring HP Storage devices. Previous version was with number 2.1.2 which hints that there are lot of changes in this management pack. Let’s take a look at the change log in the web site of HP Storage Management Pack for System Center:

  • Diagram view with health state of the HP 3PAR StoreServ Storage
  • Diagram view of the components and health state of the HP StoreVirtual Storage
  • Diagram view with health state of the HP P2000 MSA Storage
  • Diagram view with health state of HP StoreEasy 5000 Storage System with Multi enclosure Topology (JBOD)
  • Supports events and alerts generated by HP StoreEasy 1000 and HP StoreEasy 3000 Storage
  • New Product name representation of HP Storage device
Old representation New representation
HP 3PAR Storage System HP 3PAR StoreServ Storage
HP Storage P4000 HP StoreVirtual Storage
HP Storage P2000/Modular Smart Arrays HP P2000 MSA Storage
HP Storage P6000/Enterprise Virtual Arrays HP EVA P6000 Storage
HP Storage P9000 HP XP 9000 Storage
HP Tape Drives HP StoreEver Tape Drives
HP E5000 Messaging System HP E5000 Messaging System
HP X5000 System HP StoreEasy 5000 Storage
HP D2D Backup System HP StoreOnce Backup

Note:  Monitoring for HP Storage B-series Switches and HP B-series Switch Device Management Software has been discontinued from this version.

So we have these changes described in the web site which is not so bad. On first look definitely there are changes for a new major version but let’s look a little bit deeper.

Inspired by Marnix Wolf’s blog posts of Dell MP Suite I will try to review this MP in a similar way using MPViewer 2.2.1 and MPBA (Management Pack Best Practices Analyzer).

MPViewer enables you to take a quick look into any MP in order to see what it does and how. No, it won’t protect you totally from nasty and unwanted surprises but it will rule out the most nasty ones, like Discoveries which run way too often for instance. When such a thing is at hand you know exactly what overrides to make and when overrides can’t be set, you simply don’t import that MP.

Another nice thing of this tool is you’re able to export the view dump to an Excel XML file (makes it more easy to filter, count and to sort everything since per topic a tab is created) or as an HTML file making it easier to get a quick overview with the underlying code, thus revealing more information compared to the Excel XML file which doesn’t show the underlying code.

MPBPA is the tool which checks to what extend any given MP adheres to a set of Best Practices for MP Authoring. It’s part of the MP Authoring Console used for MP development in the days of SCOM 2007. Even though it’s a bit outdated it’s still a good tool to give you an insight into the overall build quality of any given MP.

Note: Description of the tools is borrowed from Marnix’s article

First let’s look at the requirements of the HP Storage management pack:

  • SCOM 2007 R2
  • SCOM 2012

So we have full support for the current and previous version of SCOM which is great. There are lot of customers who still have SCOM 2007 R2. Nothing is mentioned about SCOM 2012 SP1 because it is still in Beta but I’ve managed to install the MP on it without a problem so I guess there will be no issues with SP1. Of course do not try this scenario on production environment because it is not supported by HP.

What are the requirements for operating system:

  • Microsoft Windows Server 2003 Standard and Enterprise edition (x64 and x86)
  • Microsoft Windows Server 2008 Standard and Enterprise edition (x64 and x86)
  • Microsoft Windows Server 2008 R2 Standard and Enterprise edition
  • Microsoft Windows Server 2008 R2 SP1 Standard and Enterprise edition

As the MP is supported only on SCOM 2012 and SCOM 2007 R2 so Windows Server 2012 is still not supported. Again I’ve managed to install this MP on Windows Server 2012 without issues and as it is simple application probably there is no reason not to be working on the latest Microsoft Server operating system. Of course do not try this in production environment.

Next we need to look at what HP Storage devices are supported:

HP Storage ESL E-Series, EML E-Series, ESL 6000/9000/12000, and MSL Series

  • HP 3PAR StoreServ Storage System
  • HP P2000 G3 MSA Storage
  • HP Storage EVA P6000, 4×00, 6×00, 8×00, P6300, P6500, and HP P6000 Command View EVA Software
  • HP Storage XP 24000 and P9500 Arrays
  • HP Storage ESL E-Series, EML E-Series, ESL 6000/9000/12000, MSL Series
  • HP StoreVirtual Storage with SANIQ 9.5 and 10.0
  • HP E5000 Messaging System
  • HP StoreEasy 5000 Storage System
  • HP StoreOnce Backup
  • HP StoreEasy 1000 and HP StoreEasy 3000 Storage

As you can see there is no information on what version of firmware you should have in order this management pack to work which is quite disappointing. I can only guess that only the latest firmware versions are supported because for example on HP 3PAR StoreServ Storage and on HP P2000 MSA Storage SMI-S service should be running on 5988 port in http mode. For other requirements look at the guide that is coming with the management pack or at my previous article about this MP.

When I’ve download and extracted the files they are in the same structure and number as in the previous version – One MP guide, installation file for HP Storage Management pack and installation file for WEBES Listener. When I’ve started the installation of the MP I’ve noticed a lot of differences.

image

There are now two main options for installing this MP. You can choose to install the MP on a SCOM management server or on a server that has only the SCOM agent installed. For both options you have to have SNMP feature installed before actually installing the MP. If you choose to install it on SCOM management server or on collection point server you have to provide the path where SCOM or the SCOM agent is installed:

image

In the guide there is information how to find the right path.

The management pack has been supporting these two path in the previous versions but it was only described in the documentation and it was not provided as option in the installation wizard.

After providing the path and clicking next there is another nice surprise:

image

Now you can choose to install monitoring for only those devices that you will monitor in your environment. This hints that there are probably different management packs for the different HP Storage devices. In previous version monitoring for all devices was located in one single management pack and when you install it you get the views for all devices even if you do not use them. SCOM will also be filled with unneeded rules, monitors, discoveries and etc. that will be taking additional resources. So it seems HP has listened to its customers and improved the management pack with this best practices by dividing the MP in smaller MPs for the different storage devices. In order to verify my assumption I’ve selected only 4 devices from the list and installed the MP. The installation wizard does not provide you a location where to install the MPs but in the guide it is stated that they can be found in the following location:

image

I’ve opened the location in Windows Explorer and I’ve found the following files:

image

Only ConfigFile.xml and HPStorage.tlb files you will not find after fresh installation as they are generated when you configure HP Storage Management Pack User Configuration Tool. When looking at the files we can now confirm that there is e separate MP for every HP Storage device. This is great even for this only change it is worth upgrading to 3.0 version of HP Storage Management Pack. As the installation of the MP imports the management packs automatically in SCOM let’s see if only the selected by me storage devices have management packs imported:

image

Indeed the separation of the MPs matches with the installation wizard also. I now have only imported the management packs I need. It is great that the non-selected management packs are extracted in the installation folder. That way if you want to add a new kind of device for monitoring you can only import its management pack in SCOM.

In the guide for HP Storage management pack I didn’t saw if upgrade of previous version is supported. However even if it supported I will strongly recommend to write document every overrides you have made in your environment for the previous version of this MP. When you have that documentation it is better to remove the old version first completely by uninstalling it and deleting the management pack from the SCOM console. After you complete that task you can install the latest version, select only the management packs you need and make the same overrides you had in previous version. If you had some routing of alerts from SCOM to SCSM based on custom properties now it is a good time to change that routing based on management pack name of course if that fits your case.

Before we review every MP one by one let’s see how MPs are referenced against each other.

image

As we can see HPEnterpriseStorageLibraryMP is the main management pack and all other MPs are referencing it.

Now it is time to look at every management pack one by one with MPViewer and MPBPA:

MPEnterpriseStorageLibraryMP.mp

Looking at the main management pack with MPViewer shows that this MP defines only 4 views and nothing more:

image

So this management pack is only used as container for other views defined in the other MPs.

image

The warnings generated by MPBPA show that views are not sorted correctly and management pack elements do not have display names. Not so serious warnings but the fact that this MP contains only views and they are not sorted correctly shows negligence by the developers.

HPEnterpriseStorageStoreVirtualMP.mp

This management pack monitors HP StoreVirtual Storage Arrays.

This MP contains total number of 149 classes, 8 discoveries, 1 group, 96 unit monitors, 33 rules, 132 dependency monitors, 160 relationships and 4 views.

image

MPBPA shows a lot of errors and warnings like:

  • WMI queries should not use “Select *” statements
  • Discovery interval should not be too short
  • Alerts should have name and description defined
  • Management pack elements should have knowledge articles
  • Management pack elements should have display names
  • Views should be sorted in the expected order
  • Workflows should not use WMI queries
  • Script time-out should be 300s or more
  • Elements should not use the same display names
  • All scripts should include the US locale

image

All these errors and warnings hints that best practices are not used and this MP could affect the performance of your SCOM environment.

I suspect that all MPs will have the same errors.

HPEnterpriseStorageStoreMP.mp

This management pack monitors HP StoreOnce Backup.

MPViewer shows 1 class, 1 discovery, 9 rules and 4 views.

image

This MP is only used for SNMP alerts and because of that does not have any discoveries or diagram views.

Even that MP is very small it has a lot of errors like:

  • WMI queries should not use “Select *” statements
  • Alerts should have name and description defined
  • Management pack elements should have display names
  • All scripts should include the US locale
  • Workflows should not use WMI queries
  • Views should be sorted in the expected order
  • Script time-out should be 300s or more

image

HPEnterpriseStorageStoreEverTapeDrivesMP.mp

This management pack monitors HP StoreEver Tape Drives.

MPViewer shows 1 class, 1 discovery,9 rules and 4 views.

image

This MP is identical to the previous one. The share the same code for different devices. The errors from MPBPA are the same also.

HPEnterpriseStorageStoreEasyMP.mp

This Management pack monitors HP StoreEasy 1000 and HP StoreEasy 3000 Storage.

MPViewer shows 1 class, 1 discovery, 1 relationship, 68 rules and 8 views.

image

This MP is different the previous two mainly because it uses WMI. Because of that MPBPA also shows different errors and warnings:

  • Alerts should not use hardcoded names or descriptions
  • Alerts should have name and description defined
  • Views should be sorted in the expected order
  • Management pack elements should have display names

image

The errors and the warnings are again a lot but not so critical for the performance of SCOM to my opinion.

HPEnterpriseStorageStoreEasy5000MP.mp

This management pack monitors HP StoreEasy 5000 Storage.

MPViewer shows 9 classes, 3 discoveries, 1 group, 6 dependency monitors, 5 unit monitors, 9 relationships, 4 rules and 6 views.

image

This MP is more complicated than the previous one described. The reason behind that is because this one monitors a higher class device. Benefit of that is that you get diagram for the monitored devices.

MPBPA reveals less errors and a lot of warnings again:

  • WMI queries should not use “Select *” statements
  • Discovery interval should not be too short
  • Alerts should have name and description defined
  • Management pack elements should have display names
  • Management pack elements should have knowledge articles
  • Views should be sorted in the expected order
  • Script time-out should be 300s or more
  • All scripts should include the US locale

image

HPEnterpriseStorageP2000MSAMP.mp

This management pack monitors HP P2000 MSA Storage.

MPViewer reveals 15 classes, 3 discoveries, 1 group, 9 dependency monitors, 10 unit monitors, 14 relationships, 6 rules and 6 views.

image

Again not so complicated MP but still have the capabilities to make the diagram of the monitored devices.

MPBPA shows the same errors and warnings as the previous described MP which probably means they share the same code.

HPEnterpriseStorageEVAP6000MP.mp

This management pack monitors HP Storage EVA P6000.

MPViewer shows 4 classes, 4 discoveries, 4 unit monitors, 4 recoveries, 5 rules and 8 views.

image

This is also pretty simple MP and the reason behind that is because it relies on WEBEs Listener Service.

MPBPA shows the usual errors and warnings which are not so many:

  • Alerts should have name and description defined
  • Alerts should not use hardcoded names or descriptions
  • Discovery interval should not be too short
  • All scripts should include the US locale
  • Management pack elements should have display descriptions
  • Script time-out should be 300s or more
  • Views should be sorted in the expected order
  • Views should define a resolution state

image

HPEnterpriseStorageE5000MessagingSystemMP.mp

This management pack monitors HP E5000 Messaging System.

MPViewer reveals 5 classes, 3 discoveries, 1 group, 5 relationships, 4 rules and 5 views.

As this is again a simple MP there are not so many errors and warnings:

  • WMI queries should not use “Select *” statements
  • Discovery interval should not be too short
  • Alerts should have name and description defined
  • Script time-out should be 300s or more
  • Management pack elements should have display names
  • Views should be sorted in the expected order
  • Workflows should not use WMI queries

image

HPEnterpriseStorage3PARStoreServMP.mp

This management pack monitors HP 3PAR StoreServ Storage.

MPViewer reveals 14 classes, 3 discoveries, 1 group, 7 dependency monitors, 8 unit monitors, 13 relationships, 3 rules and 6 views.

image

MPBPA shows not so many errors and the usual big number of warnings:

  • Discovery interval should not be too short
  • WMI queries should not use “Select *” statements
  • Alerts should have name and description defined
  • Management pack elements should have display names
  • Script time-out should be 300s or more
  • All scripts should include the US locale
  • Discoveries should have discovery types defined
  • Workflows should not use WMI queries

image

As a lot of changes are introduced in this management pack it seems it is written pretty decent.

HPEnterpriseStorageXP9000MP.mp

This management pack monitors HP XP 9000 Storage.

MPViewer reveals 1 class, 1 discovery, 6 rules and 4 views.

This is another simple MP with a few errors and warnings:

  • WMI queries should not use “Select *” statements
  • Alerts should have name and description defined
  • Management pack elements should have display names
  • Workflows should not use WMI queries
  • Script time-out should be 300s or more
  • All scripts should include the US locale

image

Now that we reviewed all separate MPs there is a new service that needs to be reviewed. This new service is called HP Storage Management Pack User Configuration Tool. Quite a long name for service J. This service resembles other service of HP Management pack – HP Device Monitor service in HP BladeSystem Management pack. This new service allows you to connect to HP 3PAR StoreServ Storage, HP StoreVirtual Storage, HP StoreEasy 5000 Storage, HPP2000 MSA Storage or HP E5000 Messaging System. By connecting to these HP Storage devices with this service you will be able to get diagram view of them. This improves the experience with SCOM by providing architectures for these devices and bringing them as CIs in SCOM database. When you start the tool for first time you will be prompted to connect to SCOM server:

image

When you connect to the SCOM server you will have the option to add HP Storage System:

image

When you use the feature to add HP Storage System the following window appears:

image

From the drop down menu you have to select the type of the device. When you select it IP for that device have to be entered and also credentials to be provided in order to connect successfully. Keep in mind that for HP StoreVirtual Storage, HP StoreEasy 5000 Storage and HP E5000 Storage, only IP

Shoul be provided and for 3PAR StoreServ Storage and P2000 MSA Storage the account have to have SMI-S rights.

Summary

As a summary of all the changes introduced in this major version of HP Storage Management Pack I can fairly say that HP are on the right move. Making so many improvements on this MP in such short time shows that they are determined to provide better added value to their storage products. When you compare this management pack with the other management packs from HP you can clearly see that they are trying to provide the same experience in all management packs created by them. This simplifies the experience of installing and configuring their management packs and increases the experience of using them. With changes introduced we can see that HP 3PAR Storage is the flagmen product of these storage devices and improvements for monitoring it will continue to be developed by HP. I strongly recommend to upgrade to HP Storage Management Pack version 3 if you are still using one of the old ones.

The latest version of HP Storage Management pack you can download from here.

All the reports from MPViewer and MPBPA you can download from my SkyDrive.

Advertisements

36 thoughts on “HP Storage Management Pack Updated to Version 3.0 – Review

  1. HP storage old MP pack already installed that need to remove .How can remove HP storage MP from SCOM 2007 , what steps need to follow and what is effect to Management point , Root server and other MP.

    1. Uninstall the installation. This installation actually just copies the management pack in folder in program files and imports the mp.
      After you uninstall you have to remove the MP directly from SCOM 2007 console. Any override management pack will also have to be removed. After these two steps you can proceed with installing the new version.
      Affect on servers will be that you will not have monitoring for your HP storage during that period.
      Remember that you have to configure the new MP all over again and all overrides have to be made again.

  2. Hi Stanislav – Great write up.
    Did you try installing Collection Point Server? When I tried installing it, it won’t enable the path to select and defaults to C:\ and finally installs under C:\ProgramFils(x86)\HP\EnterpriseStorage.
    I haven’t seen any service running after this is installed as Collection Point Server. SCOM Agent is running on this machine. How would SCOM agent knows about this server?

    I couldn’t find what port is used to connect to SCOM server? Also, it is not clear how it works under GW server when it is in untrusted domain with SCOM domain.

    Traps from Storage Nodes are reaching the server where Collection Point Server is installed.
    When it was installed first time, I could see a VirtualStore.log file which was recording the traps, but when the installation was repaired or re-installed this file disappeared 😦

    Any pointers would help.

  3. Hi Raja,
    I haven’t tried Collection point server. How I imagine this is that you have that HP Storage Management Pack User Configuration tool on one of your MS or on your RMS server in order to populate the objects (fans, hdds and etc.) from storage devices in SCOM. The collection point is your server where you will send SNMP traps from these storage devices. As these traps are only SNMP you only need SNMP service and the installation probably install the needed MIBs for these devices and probably some registry key that SCOM discovers and knows that this server is a Collection Point server. I am not sure about this but this is my logic how this solution works. I may try to verify this in my test environment. Of course I cannot verify it completely as I do not have HP Storage at home 🙂

  4. Hi Stanislav,
    It worked fine after after restarting the server and re-installing the Collection Point Server package on a node that has SCOM Agent running. Test traps from Storage nodes are shown on SCOM server.

    Any idea on which port HP Storage Management Pack User Configuration Tool connects to SCOM server?

  5. Hi All,
    I have the same problem with SCOM 2012 SP1 installed on Server 2012. I have tried it also on SCOM installed on Server 2008 R2. I have checked If the traps can reach both machines. This is working. But I found in the log of the Health Service this entry. The installation was exactly doen as descripet.

    —————–

    Module was unable to execute the notification query.

    Error: 0x80041010

    Details: Invalid class

    One or more workflows were affected by this.

    Workflow name: HPEnterpriseStorageP2000MSAMP.WarningAlertNotify.Catcher.Rule

    Instance name: HP P2000 MSA SNMP Trap Catcher Discovery

    Instance ID: {2F6A95D6-E439-FEEF-AC60-928E8C6CB158}

    Management group: SCOM2012

    —————————————-

    Any Idea how i can fix this?

    Rgds,

    markus

  6. Hi Markus,
    have you fixed your Problem because i have the same Problem. Scom2012 Sp1 on Server 2012.

    Regards
    Wolfgang

  7. Hi Wolfgang,

    no, the Discovery is not running.The result is an empty diagram view. SNMP Events are working.
    I have installed the HP Software on a Windows 2008r2 machine now to get the SNMP part working. The first trial was that I have installed the HP Software on the SCOM MGMT Server which was an Server 2012. The strange issue was that after enableing of the Discovery rule no SNMP traps were received on the Server. Aftzer disableing of the rule SNMP was starting again to receive SNMP traps from the MSA….
    Regards,

    Markus

  8. Hi
    Tested the latest version of this pack and quite disappointed as… whilst saying this is compatible with SCOM 2012, I doubt it is. SCOM 2007 and 2012 have a major difference in the way the SNMP trap are handled :
    in SCOM 2007, the trap are received by the SNMPTrap service under Widnows listening on port 162.
    in SCOM 2012, this windows service NEEDS to be disabled (contrary to HP installation guide, referring to old SCOM 2007 way of doing) and SCOM 2012 actually has its own process listening on port 162.

    What this means is that whilst I am fully able to receive traps or query SNMP from SCOM on manyd devices. Nothing ever occured for D2D Storage after half day testing. As the HP instuction of the manuals are fundamentaly contradictory with a good setup of SCOM 2012 for SNMP handling and because of the classes used by this management pack seems still referring to the 2007 version, I doubt it can ever work.

    I uninstalled all waiting for HP to release a properly designedmanagement pack for SCOM 2012.

    1. Hi Stephane,
      I understand your frustration. The MP is not quite easy to setup, the guide could be improved a lot also. In situation with SCOM 2012 I would install the MP and the SNMP service for the MP on a server that is not SCOM Management Server. This is beacuse you will probably use the management servers in a resource pools for network monitoring and it is not recommended to install the SNMP service on them.

  9. Greetings,

    For those who manage their 3PAR array in Hyper-V environements using SCVMM 2012 SP1; note that there is a new version of HP Storage UI Add-in for SCVMM 2012 SP1. The Stirage Add-in from HP provides you single pane of view for all storage related informations that will influence your decisions from provisioning perspective in SCVMM environement.

    Link to freely download:
    https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=System_Center

    Key features of this add-in:
    1. Provides overview screens containing information of HP 3PAR StoreServ arrays, hyper-V Hosts and VMs.
    2. Provides context sensitive in-depth information for relevant volume and their local and remote copies.
    3. Provides feature to expand base 3-PAR StoreServ Volumes.
    4. Shows Adaptive Optimization (AO) policy details for HP 3PAR StoreServ arrays.
    5. Extracts alerts from System Center Operations Manager, generated by HP 3PAR StoreServ arrays.
    6. Provide detailed path information of VMs up to storage arrays.
    7. Provide information of StoreOnce.
    8. Provide option to export the storage details to .csv file.

      1. Hi Stanislav,

        Thanks for your feedback. I tried reaching you through your HP email id. Seems its not working any more. Can you contact me over email.

  10. Has anybody got this working on an HP EVA ?

    I have gotten to the Add Storage Device but cannot see my device. There is mention in the Docs that WBES/SEA needs to be installed and configured for command view but the pack (v3)only comes with WBES but not SEA and according to HP you cannot download it individually. Am I missing something?

    1. Hi,

      HP Storage Management Pack for System Centre supports only events/alerts for P6000 EVA storage. HP Storage User Configuration Tool is used to add the data of Storage devices for Diagram view, since For P6000/EVA diagram view not supported hence entry is not seen.

      Configure the P6000 EVA to monitor the alerts/event please refer “Configuring the Management Pack for HP EVA P6000” in page 49 describes the details of configuration for monitoring P6000 EVA system. WEBES 6.3 will be available as independent component, will be post the link to the same.

      1. Thanks Manju, I will take a closer look. Ended up using the HP Performance monitor which works well but now have the 2003 issue where SCOM just stops logging. Its a known bug but I thought I would try….well it worked for zenoss!

  11. Hi Stanislav,

    Thanks for the post, however I’m hoping you can help me with an issue I’ve come across applying this pack? I’m running SCOM 2012 R2 with v3 of the Storage pack and installed the SNMP Collector on an agent managed server. However when I installed the management packs and enabled the 3PAR SNMP Trap Catcher discovery I did it against the Windows Computer Class instead of the specific server I wanted to target. Now all computers running the service SNMP TRAP are showing as discovered inventory generating alerts of OpsMgr failed to run a WMI Query for WMI events.

    I tried to stop this by creating a new override for disabling the discovery and setting it to enforce. Then using the Remove-SCOMDisabledClassInstances cmdlet but it’s made no difference.

    I’ve also tried clearing the cache on individual agents.

    Any ideas?
    Thanks

    1. Hi
      I would do exactly the same thing you’ve done but it seems does not work. Have you tried removing all overrides related to this discovery and than run the cmdlet?
      Another option would be to create a group with all servers and make override against that group to disable the discovery. In that group you can exclude the server with the trap catcher. And run the cmdlet again?
      Third option would be to completely remove the management pack run the cmdlet and add it again.
      Hope this will be helpful.

  12. Hi i have a problem with 3.1 version of this MP and was hoping that you could help me with it.
    I installed the collector on an agent managed server and the management pack (first choice in the setup) on a SCOM management server; added 2 HP P2000 to MP user configuration and their events does show up in SCOM console. the problem is that nothing shows up in diagram OR state view. the storage device just doesn’t show up in scom.
    i would appreciate any tips to get this to work.
    thanks.

    1. Hi,
      You should the P2000 devices in HP Storage Management Pack User Configuration Tool. Have you seen this: https://cloudadministrator.wordpress.com/2012/12/21/hp-storage-management-pack-updated-to-version-3-0-review/
      If you’ve done that make sure you have powershell on your collection server. If there is not powershell installed you will see Event ID 21400 in Operations Manager Log.
      If that is not the case look for error in the Operations Manager log on the collection server.

      1. Hi,
        The MP is installed but when using the HP Storage Management Pack User Configuration Tool.exe it is looping on the account created by our Storage administrator.”Please enter the Username of the SMI-S Provider of the Storage System that needs to be discovered.”
        It is a local account create on the storage? Should it be a domain account? SMI has been enabled for this account, which other rights/permissions should have this account? on the storage? on the RMS?
        Thanks,
        DOm.

  13. Hey man, thanks for your answer. i looked in the logs and turned out the discovery script timed out before it had a chance to complete. i had 2 devices in MP User configuration tool. removed one of the P2000 and discovery completed and device showed up in SCOM Console. The new problem is that when i try to add a new device in MP User configuration tool ( the device i previously added without any problems) it shows that the device timed out. in system central forum you talked to a guy who had a similar problem and the port was causing the issue. do you have any idea have can i fix this one ?

  14. Hi All,

    I digged a lot around this HP MP… Here’s my conclusions:

    EVA P6000: The Webes/SEA service is not available anymore. HP discontinued the product. You should use HP IRS to manage you EVA hardware. I setup the HP EVA Management Pack v. 3.0.0.225, who monitor performances through evaperf. Quite old, but worked at 90% Only 2 monitor included by default that can trigger alarms (Write and processor)

    P2000: For SMI-S, you have to choose between IRS and SCOM. IRS use HTTPS 5989 instead of SCOM using HTTP 5988. I still have the event:
    Workflow name:

    HPEnterpriseStorageP2000MSAMP.CriticalAlertNotify.Catcher.Rule
    Instance name: HP P2000 MSA SNMP Trap Catcher Discovery
    Instance ID: {32F6F899-285F-742C-E8C7-6568830DE57D}

    I wish HP to increase the quality of their MP, but as they have their own tool for monitoring, my guest is they not give much importance to it!

    1. Hi Christian
      My name is Amit Kumar and I manage the HP Storage Management Packs for SCOM.
      I wish to inform you that we are working on fixing the EVA alert monitoring through IRS instead of WEBES.
      Regarding the MSA P2000, we plan to continue alerts monitoring and topology view through the robust SMI-S Provider.

      I wish to work with you directly and hence request you to mail me directly so that we can take this discussion forward.
      We are continuously aspiring to improve the customer experience in single pane monitoring of HP Storage systems though SCOM.

      Thanks
      Amit

      1. Hi Amit, Any chance That you have a solution to my problem? My problem was that when i had 2 devices in MP User configuration Tool the script would time out before it had a chance to complete (2 MSA P2000). when i removed one of them from MP USer Configuration, the other one was discovered in SCOM Console. now when i want to add another device to MP user configuration, it just times out. 2 comments higher i explained this in detail.
        i would really appreciate any help.

      2. Hi Amit,

        I agree P2000 should still be monitored by SMI-S, but is it possible to change check port for SMI-S to have both monitoring tools (IRS and SCOM) displaying the messages? (IRS 5989, SCOM with HP user configuration tool 5988. THe latest framework version allow to change SMI-S to only 1 port…)

        THank you for the update about WEBES/IRS, pretty interesting! Could be good if you can integrate the following management pack in it

        http://www.systemcentercentral.com/pack-catalog/hp-eva-performance-management-pack-v3/

  15. MJ,
    Please log a call at HP support and I will be glad to assist you, we also need to check the model #, f/w versions etc for your setup.
    Is the discovery of MSA behind a gateway server and SCOM and MSA are in two different subnets?
    What is your discovery interval seconds before timeout set for the MSA rule ?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s