Configuring HP BladeSystem Management Pack for SCOM

Most of the large organizations today do not buy individual servers (exceptions are present of course) instead they buy Enclosures. In one such enclosure you can put up to 16 server and/or storage blades. HP as one of the biggest hardware vendors offers two such solutions – HP BladeSystem c3000 and HP BladeSystem c7000. If you bought such solution you receive for free HP BladeSystem Management Pack from HP for SCOM to monitor HP Enclosures. To start monitoring you HP Enclosures of course you have to first install and configure that MP on your SCOM environment. HP is providing installation and configuration guide for the management pack but I will walk you trough the steps you need to perform if you stumble on some difficulties. These steps are applicable for SCOM 2007 and 2012 versions:

1. First you need to download HP BladeSystem MP. You can find it here. The MP is part of Insight Control for Microsoft System Center solution.

2. After the MP is downloaded it is best to install SNMP Services feature on your RMS server (RMS Emulator). As in 2012 you have RMS emulator and you can move that role to other Management Server it is good idea to install SNMP Services on another Management server if you want to failover in case your RMS Emulator server goes down. SNMP Services installation does not require restart.


3. The HP BladeSystem MP when it is downloaded is archived in a zip file in which you can find several files – 64-bit installation file, 32-bit installation file, License agreement file, Release notes file, User guide and Troubleshoot guide. When you unzip it copy the 64-bit installation file (these days there are not many 32-bit SCOM servers Smile ) to your RMS server.

4. Start the 64-bit installation. Keep in mind that this management pack have certain requirements – HP ProLiant Server Management Pack imported (I will describe installation and configuration of that MP in another article), Windows PowerShell 1.0, .NET 2.0 Framework, SNMP Trap Service (We installed it in step 2) and of course at least SCOM 2007. Finish the installation with the default settings. It is pretty simple installation. If you have SCOM 2012 you perform the installation on the your failover Management Server also.


5. After the installation is finished you will see two new service and one application installed:



6. Next step is to configure SNMP. Open Services console. Find SNMP service and double-click on it. A dialog box will appear on which you have to click on Security tab:


7. You have to check Send authentication trap option. Add community name that you will use for communication between the RMS server and the enclosures. You can use READ ONLY rights.

8. Select Accept SNMP packets from these hosts and add all your IP’s of your Onboard Administrators (Primary and Secondary). Onboard Administrator is the control interface from Enclosures. Click OK when you are done. Now the RMS server is configured to receive SNMP packets from the Enclosures you will monitor. If you are using SCOM 2012 you can make the same settings on your Management Server that you will use for failover of your RMS Emulator role.

9. Next step is to add your HP Enclosures to HP Device Monitor Console. You can find that console in Start Menu -> All Programs -> HP SCOM Management Packs.

10. When you start it you need to make a connection to localhost, FQDN (of your RMS server)or NetBIOS name (of your RMS Server). The console actually connects to that HP Monitor Device Service that is installed on the RMS.

11. After you are connect to that service trough the console on the right of the console you will find Actions menu from where you can select Add Onboard Administrator option.


12. Click on Add Onboard Administrator.

13. A new dialog box will appear where you have to add IP address or FQDN of your Onboard Administrator. You also have to provide your administrator username and password to your Onboard Administrator interface.


14. Add all your Onboard Administrators to the console using steps 12 and 13. Adding OAs in the console will discover all components of your Enclosures and will draw SCOM diagrams for them. If you have SCOM 2012 you can connect the HP Device Monitor Console to your failover Management Server and add the same OAs there.

15. The final configuration step is to configure OAs to send SNMP traps to the RMS server. This can be achieved by opening OA web interface. When you open the interface you have to expand Enclosure Information than expand Enclosure Settings and finally click on SNMP Settings. Check Enable SNMP option, fill the other fields and click Apply. For Read and Write community name use the one entered you’ve used in step 7.


16. Now that SNMP is enabled we have to configure OA to send traps to specific IP address. Right beneath Enable SNMP settings there is SNMP Alert Destination setting. For host you have to enter the IP address for your RMS server and for community name enter the one you’ve used in step 7. Click Add. There is Send Test Alert button which will send trap to your RMS server and will appear as warning alert in SCOM console. This is very handful option to verify that your configuration was successful.


17. Repeat steps 15 and 16 for all your OAs.

When you complete your configuration you can use Send Test Alert option to see if all enclosures are configured correctly and are receiving alerts. You also should be able to use all your enclosures by opening the SCOM console, navigating to Monitoring pane –> HP Systems –> HP BladeSystem Enclosures –> Enclosure State:


Note: HP BladeSystem Management Pack should be imported during the installation. If for some reason this is not done you can import the MPs manually by finding them on the RMS server in the installation folder of the MP. This also refers to HP ProLiant Server Management  Pack.

If you have SCOM 2012 and your RMS Emulator server fails you can follow two steps to recover your monitoring for HP BladeSystem Enclosures:

1. Transfer RMS Emulator role to your failover Management Server

2. Change the IP address of your failover Management Server to the IP address of your failed RMS Emulator server because SNMP traps are send to specific IP address. If you do not want to change the IP address on your Management server you have to reconfigure all OAs to sent SNMP traps to your new RMS Emulator.

Note: HP BladeSystem Management Pack does not require to be installed on RMS server (RMS Emulator). It can be installed on any SCOM Management Server or Server that have agent installed but is common practice such monitoring solutions to be installed on RMS. Also the documentation of the management pack doesn’t mention that the MP relays on the RMS (RMS Emulator) server to function properly.

141 thoughts on “Configuring HP BladeSystem Management Pack for SCOM

  1. Thanks for posting detailed steps. I am wondering if my deployment configuration is SCOM 2012 -> GW Server -> Blade enclosures, where should I install HP MPs. My SCOM and GW server are in two different untrusted domains.

    1. Hi Raja,
      The MP can actually be installed on any server. It doesn’t have to be an SCOM server. You can a specific on which the Blade MP to be installed an enclosures to be monitored from there. If you have a small number of enclosures 10-20 you can consolidate the Blade MP with some of the SCOM servers. If you have a lot of enclosures it is best to have separate server for monitoring them in order not to affect performance on any SCOM server.
      If your SCOM servers and your SCOM GW server are in different subnets over WAN and if you have enclosures in both subnets it is best to install the Blade MP on one of your SCOM servers and on the SCOM GW as well. The enclosures that are in the subnets with the SCOM server you will monitor with the SCOM server and the enclosures that are on the subnet with the SCOM GW server will be monitored by the SCOM GW server. Of course if you have enclosures only in one location you will monitor them by the closest server whether it is the SCOM server or the SCOM GW server.
      Even if you have enclosures in two different location you can still monitor them by one server.
      So basically you have multiple scenarios that you can use. Let me know if I explained it well if not please write detail information about your environment (enclosures, locations, data centers, scom servers) and I will propose you solution.

      1. Thanks Stanislav for a quick reply. In my environment, SCOM and GW server are in two different domains connected over WAN as one of the configuration scenario you mentioned rightly. All my to be monitered servers are in GW server (service forest) domain. If I understand what you are saying correctly, this is what I should be doing. Please validate my approach/steps.

        1) Enable SNMP service on GW server
        2) Install HP Management Packs on GW server. ( I read somewhere that no MP can be installed on GW server)
        3) Configure SNMP to accept traps on GW server
        4) Configure SNMP on Enclsoure to route snmp traps to GW server. Is this correct?
        5) I also assume, that each monitoring server should have HP Insight Agent installed..I know it is basic question, but just wanted to be sure nothing is missed 🙂

        Now how this information is routed to SCOM console? Should I install MP on SCOM server as well? In my setup GW server can communicate ONLY to SCOM server over port 5723 and can’t reach db server etc.

  2. Hi Raja,
    1 – Yes
    2 – Yes. The installation will install the the service that monitors enclosures. Remember that there are different MPs for monitoring enclosures (uses HP service and SNMP to monitor them) and servers (uses SNMP OR WMI to monitor servers). I cannot verify of BladeSystem HP cannot be installed on GW. After the installation on the gateway you have to check if the management packs are imported in SCOM. If they are not imported import them manually.
    3- Yes accept traps on GW servers from enclosures.
    4 – Yes
    5- If you want to monitor the servers that are in enclosures also you have to install the HP agents on the operating system. Depending on what method of monitoring these servers you want – SNMP or WMI there are different agents and different settings in SCOM console.

    You do not have to install the MP on the SCOM server you just need to import the MPs if they are not imported. SCOM will find the server where the HP custom service is installed for monitoring enclosures.

    Please check in the documentation guide if installation of the MP is supported on GW. To me it should be supported because GW is basically a super SCOM agent but may be there are some restrictions.

  3. Thanks much for the reply. Will update once I test this scenario. We found that the monitoring servers doesnt’ have Insight Agents installed and in the process of installing the same.

    1. Thanks for
      I configured Blade System Management Pack and can see Blade Enclosure diagram, bays etc in SCOM 2012. When I send a test alert from Enclosure, that alert is not seen in SCOM 2012 console. Not sure how to debug this. Any help is appreciated.

      1. Still the Alerts issue couldn’t be resolved. I am guessing that there is some problem with Run As Account for HP BladeSystem Enclosure Monitoring Account configuration. I have configured a Run As Account with the username and password that has admin rights on GW server as my HP DMS is running on GW Server. There are no errors either in GW server or SCOM server. Any thoughts?

  4. Hi

    When i installed the HP BldeSystem Management pack , it installed HP BladeSystem Enclosure Monitor manager instead of HP Device Monitor Console

    I dont see the HP common Service either. Instead i see HPBladeSystemEnclosureMonitorService

    Did i do something wrong.

    I installed HPBladeSystemMP01_40(x64)

    1. Hi Kitaab,
      You are using older version of the management pack. In some of the latest versions HP BladeSystem Enclosure monitor manager was changed to HP Device monitor console. I suggest to use the latest MP that you can find here:
      or here :

  5. When i installed , it extracted the Management packs which Included :

    Which are considerations of your other post.

    Do i have to still Install the HPProLiantMP01_60(x64).exe

    By the way that is not part of this

    When i downloaded this i could see only this for SCOM

    Do you mean i have to Install HPSCOMManagementPacks-x64.exe and then on top of it Install HPProLiantMP01_60(x64).exe as well

    I am asking this because all my discovered HP windows servers show not monitored.

    1. HP insight control is a full solution to integrate hp insight control with System center. It contains MPs for SCOM, packages for SCCM and etc. You should install only one of the exe files. They should be the same latest version of the MP. I do not know why they show as not monitored. I will need more information if you want to help you. Which HP agents are installed on the servers. Which versions? Is scom agent installed on the servers. Is the scom agent able to monitor servers for other MPs? Have you configures some overrides in the HP MP? WHich method you will use for monitoring WMI-based or SNMP-based?

      1. Thank you for the update , i checked this morning and servers do show monitored.

        I think it took very long to calculate the state thats it.

        I believe we do not need to follow the 2nd post (except for Override Part if someone need that)

        It would be great if you post regarding how to use this MP for monitoring Unix/Linux and VMware based servers as well.

  6. Yes. Sometimes you have to be patient until discoveries kick off. Override is necessary if you want to monitor your server with WMI-based method. HP recommends using SNMP based method and that is why SNMP method is the default method. I prefer WMI-based.
    I do not have experience with HP hardware monitoring of Unix/Linux and VMware monitoring that is why I haven’t publish any article.

      1. Blade Enclosure in SCOM were discovered via Device Manager Service installed on a Gateway Server. Logged into Enclsoure OA, configured SNMP trap destination as GW server. When a Test SNMP trap is sent from Enclsoure OA, nothing is seen on SCOM.
        I configured snmputil to check if traps are recieved or not and don’t see the traps on the snmputil console. I am double checking whether the ports are open or not.


      2. Hello,
        Now I can see the traps from Enclosure in snmputil where HP device monitor service is installed; but the trap is not shown in HP Device Monitor service log or on SCOM server. Is it required to import Enclosure SNMP MIB on the server where HP Device Monitor is running? Or any other step is missing?

        1. Hi Raja,
          Apologies for the delayed reply. I do not think import of any MIB is required. It is not mentioned in the documentation. If it is required it should be imported during the installation of the MP but once again I do not think it is required. If you receive SNMP traps I would double check SNMP Service settings if everything is configured OK and SNMP service is not rejecting those traps. You can also check if you do not have any other SNMP service (3rd party) installed and running on the server. If settings are OK may be it is time to contact HP Support.

      3. Thanks Stanislav. I am seeing “- SNMP Event Log Extension Agent has terminated. Event 2020.” message in Application log where Device Monitor Service is running Once trap is received, is it automatically routed to DMS? I don’t know how DMS registers with Trap service to get notification of traps. No other event logs are logged.

        Device Monitor Service is on a Windows 2k8 datacenter edition server on a vmware Virtual instance in a HP Blade server.

        1. Hi Raja,
          If I remember correctly the HP Device monitor service was only used for discovery of the enclosures and their objects (fans, etc.). The enclosures sent traps to the SNMP service. The snmp service logs the event and the agent registers it in SCOM. The event ID you are postings is a purely SNMP event which seems you have issues with SNMP service. Over Internet I’ve managed to find this hotfix
          and this discussion
          If this hotfix is applicable to your server may be it is a good idea to install it as it seems your issue is similar.

      4. Wouldn’t HP Device Monitor Service show its dependency on SNMP Trap Service as its function is dependent on it?

      5. As per HP Device Monitor document:

        The HP Device Monitor performs the following functions:
        • Initiates a connection to the monitored device
        • Receives SNMP traps from the device
        • Collects server subsystem state
        • Collects enclosure component state
        • Collects hardware inventory
        The HP Device Monitor Service uses the information entered through the Device Monitor Console to connect to and monitor HP hardware. If the connection succeeds, the HP Device Monitor Service continues to monitor the device for inventory, health state, and events.

        This clearly states that this service provides health state and events, hence it is used for monitoring.

        Thanks for the link from Microsoft site, but the fix provided was only for Vista, Win 2k.
        It is interesting that in that thread who all complained are running the server on HP Hardware. Don’t know if this is a problem only on HP devices, blades or VM instances.
        Will continue to explore

      6. Hi Stanislav – After recycling HP Common Services, traps started showing up in SCOM console. Thank you so much for all the support and time…

        btw, in a GW server environment, it is not advised to have HP Device Monitor Service installed in GW server. This was mentioned in HP Device Monitor documentation. For me also it worked only after the DMS is moved to another server with SCOM agent under GW.

        1. Hi Raja,
          I am happy that everything is working OK now. I think you’ve managed to troubleshoot it very well. Thank you very much for the information of DMS and SCOM GW. If you have any other questions or issue let me know and I will try to help with whatever knowledge I have. Have a nice day.

  7. Question: In my environment I’m running SCOM 2007 R2 CU6 and have a single RMS cluster – no other management servers or gateways. The Exchange 2010 management pack and associated service runs just fine when installed correctly. Can the HP Blade Management pack be installed as cluster-aware or so it runs properly on an RMS cluster? I saw another post by someone complaining they were not able to get it to work right… I’m gonna try it here in a bit – I assume I can simply install it on each node while it has the RMS role and configure the service as part of the cluster application resource. I’m just curious if anyone has actually done it…

    1. Hi John,
      I do not know a person who actually have done it but in the documentation for HP BladeSystem states that you can cluster the service. You just have to configure the SNMP rules on both servers and configure Onboard Administrators to sent SNMP traps to both servers. The service will be up only on one of the nodes so only alerts from the active node will be received. What you have to think is if you add new enclosure in the HP Device Monitor console you have to failover the service to the other node and add it also there. If you decide to try it I will be happy if you share your results.

  8. I installed this Blade management pack etc on my server which was running the HP Storage Management Pack. SNMP Traps are not received anymore when this HP Device Monitor service is started. So the DMS and the HP Storage Management Pack User Configuration Utility cannot run on one server implementation?

    1. Frank, Did you check the file HP\HP Enterprise Storage\HPStorageVirtual.txt ? All the traps received from Storage Devices are recorded in that file.

  9. When I try to add an onboard administrator in the DMC. It says “Unable to configure device with DMS. For error details see event log.”
    This is the event log:
    “[3/5/2013 11:36:38 AM PID=4636] (DeviceNotFound) Event: The HP Device Monitor Service was unable to discover the device.
    Please check the connection and configuration for the device and try to discover the device again.
    Could not discover or identify x.x.x.x.
    Ensure the device is up and connected to the network.
    Ensure the credentials are correct by verifying the community string for SNMP managed devices.
    Ensure the Insight Management Agents are currently running on in-band server devices.
    Ensure the Agentless Management is configured properly in the iLO Management Engine for out-of-band server devices.”

    SNMP is installed and configured.
    DMS is running.
    MP’s are installed.

    I’m able to login at the webinterface but not adding something in DMC.
    Any suggestions for this issue?

      1. I opened it from different places (also where the DMS is installed) the OA web interface is perfectly running. Already restarted the service. That does not help a bit. We have two blade c7000 enclosures both have the same errors. I’m not able to login in DMC on both devices is unable to configure device … error. There are no firewall/acl rules. The DMC&DMS, SCOM is running on the same server.

        1. Hi Wago,
          In order to provide you some hints with the troubleshooting I will need more detailed picture of your environment:
          SCOM version?
          How netwrok is connected?
          version of Blade Enclosure MP and DMS service?
          Where is DMS installed? On SCOM server or in separate server?
          Errors from eventlog?

  10. I’m working with SCOM 2012.
    For the network: core switch -> server switch -> blade enclosure.
    The SCOM server is connected with the server switch.
    Hewlett-Packard BladeSystem Management Pack
    The DMS is installed on the SCOM server.

    This is the event log:
    “[3/5/2013 11:36:38 AM PID=4636] (DeviceNotFound) Event: The HP Device Monitor Service was unable to discover the device.
    Please check the connection and configuration for the device and try to discover the device again.
    Could not discover or identify x.x.x.x.
    Ensure the device is up and connected to the network.
    Ensure the credentials are correct by verifying the community string for SNMP managed devices.
    Ensure the Insight Management Agents are currently running on in-band server devices.
    Ensure the Agentless Management is configured properly in the iLO Management Engine for out-of-band server devices.”

    20130307-140923:7860:INFO:ui.server: – – [07/Mar/2013 14:09:23] “HTTP/1.1 POST /discovery/” – 401 Unauthorized
    20130307-140949:7860:INFO:ui.server: – – [07/Mar/2013 14:09:49] “HTTP/1.1 POST /discovery/” – 404 Not Found
    20130307-141004:12524:INFO:ui.server: – – [07/Mar/2013 14:10:04] “HTTP/1.1 POST /discovery/” – 401 Unauthorized
    20130307-141030:12524:INFO:ui.server: – – [07/Mar/2013 14:10:30] “HTTP/1.1 POST /discovery/” – 404 Not Found
    20130307-141040:12884:INFO:ui.server: – – [07/Mar/2013 14:10:40] “HTTP/1.1 GET /entity/oa” – 401 Unauthorized
    20130307-141040:12884:INFO:ui.server: – – [07/Mar/2013 14:10:40] “HTTP/1.1 GET /entity/oa” – 200 OK

    This is what is I get from the hpcs when I restart the service:
    20130307-142442:9556:INFO:root:CommonServices shutdown
    20130307-142442:3020:ERROR:util.dns:asyncdns loop exited
    20130307-142445:8768:INFO:root:CommonServices startup (version
    20130307-142445:8768:INFO:root:Runtime: 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)]
    20130307-142445:8768:INFO:root:Loading configuration (/Program Files/HP SCOM Management Packs/HP Device Monitor Service/HP Common Services/share/config.xml)
    20130307-142445:8768:INFO:root:Configuring database
    20130307-142445:8768:ERROR:bubbles.xsd.schema:Schema Validation Error: :8:0:ERROR:SCHEMASV:SCHEMAV_ELEMENT_CONTENT: Element ‘{urn:datatypes.xsd}types’: This element is not expected. Expected is ( {urn:datatypes.xsd}password ).
    20130307-142445:8768:INFO:root:Configuring event subsystem
    20130307-142445:8768:INFO:root:Loading plugin: hp.plugins.discovery
    20130307-142445:8768:INFO:root:Loading plugin: hp.plugins.oa
    20130307-142446:8768:INFO:root:Loading plugin: hp.plugins.server
    20130307-142446:8768:INFO:root:Starting all plugins
    20130307-142446:8768:INFO:root:Starting SNMP and WBEM listeners
    20130307-142446:8768:INFO:root:Starting webserver
    20130307-142446:8768:INFO:root:Starting scheduler
    20130307-142446:8768:INFO:hp.base.scheduler:Scheduler start
    20130307-142446:8768:INFO:root:Restoring persisted data models

    1. If you monitor network devices from the SCOM where DMS is installed I would suggest to uninstalled DMS from that SCOM servers and remove SNMP feature. It is not recommended to install SNMP feature on SCOM server that monitors network devices. This is because SCOM has its own SNMP builtin. Install HP DMS on server that is not SCOM or a SCOM management server that is not part of a pool for monitoring network devices.
      Also it seems that when you restart the DMS service you get some error in the log. I would try to re-install the service.

      1. I add it by IP what would be the difference when I add by dns name. If I would by dns should I use FQDN?

      2. Added it by FQDN now it works. Thanks for the help. I have no idea why it wasn’t possible to add by IP address.

  11. Unfortunately I have the same problem as WagoL had. I cannot add a OA. Tried using dns and IP but no difference. Logfiles look the same (404 error in HP Common services)
    Tried running the service on a Windows 2012 Server (scom management server) and on a 2008R2 server (no scom roles)
    We are running OA version 3.71

          1. No firewalls between server and OA (other than windows firewall on the server). We are using a proxy to connect to the internet (automatically configured through wpad) local adresses are excluded from prixy use but even without the proxy enabled I still get the message. And we can access the OA webpage from the same machine (s)

            1. The HP service uses its own configuration for proxy os in order to set proxy for the service there was one configuration file that you need to edit. I think it was described the installation guide. See if you can find it. If you are not able I will try to find it later when I get back from work.

              1. I couldn’t find any references to proxy use.
                However I did install a new server, put it in the same network/vlan as the OA, and made sure no proxy is involved. Unfortunately I experience the same, and cannot add an OA to the device monitor service.

                1. Hi Erik,
                  Previous version of HP Device monitor service was called HP Bladesystem enclosure monitor service. And in the guide for that service there was a section on how to configure a proxy for the service. You can find the guide here .On page 36 you can see the steps how to configure the proxy. You just have to see if there is such configuration file in the new service. If that does not help I suggest you to turn over to HP for support as I am not familiar with your environment. I never had issue with adding OA in the console. One more tip you have to be administrator on the server to add OA to the console.

  12. If you run into the 404 error, please check that the ‘Enable XML Reply’ option is enabled for the enclosure (Enclosure settings -> Network Access)

  13. Hi,

    excellent guide (both of them tbh).
    I get test alerts fine, but I can’t see the health of the enclosures in the Enclosure States (it’s blank) 🙂

    Any tips?

    1. I think I’ve had this issue in the previous versions of the MP. In the new ones it should be fixed. Are you using the latest version of the Enclosure MP and HP Device Monitor service. In my case happened when I had more than 10 enclosures added. How many enclosures do you have added? I’ve fixed it manually by removing enclosures one by one from HP Device monitor console and adding them again.

  14. Hi Stanislav

    I hope you can help me maybe. I try to monitor a HP Blade Enclosure c7000, but i can’t add it on the HP DMC. Evry time I tried I got the error 440. Between the HP DMC and the Blades are some Firewalls with open Ports (80,443,snmp). My question does I need an additional port?

    Thanks for helping.

  15. Yes it’s enabled.
    For additional information I have installed the DMC on a
    SCOM GW Server,
    On the second DMC in the untrusted Zone the same Firewall Configuration will work.

    Thanks for help


  16. Hi Stanislav

    Does I need these Ports,5989, 50443 Netbiosname? I analyzed the Firewall Logs,and these Ports are blocked by the Firewall.
    When you need more information, tell me.

    Thanks for help


  17. Hi,

    I hope you can help me. I configured the HP BladeSystem Management Pack ( as described in the manual with DMC on my Management Server and DMS on a different one and correct SNMP settings on the servers and on OA.

    The device bay state view in SCOM console is empty, the only thing I’ve found was in the event log “HP Device Monitor”, what does this mean and how can I correct it?

    LogName: HP Device Monitor
    EventID: 250
    Level: Warning

    The device instance has not been restored. HP Common Services may have been restarted resulting in this condition. The device instance should be updated and this condition corrected in a future polling cycle.
    Onboard Administrator: XXX.XXX.XXX.XXX; Error code: NonAuthoritativeInformation

    BG Mario

          1. An update to the latest firmware version is not planned yet 😦

            In the HPDeviceMonitorCmdlets.log I found this:
            2014-02-05 09:32:56.0585 powershell 8104:6 WARN GetListDisocveredOASummaryEntities The device instance has not been restored. HP Common Services may have been restarted resulting in this condition. The device instance should be updated and this condition corrected in a future polling cycle.
            Onboard Administrator: XXX; Error code: NonAuthoritativeInformation

            I’ve tested the powershell cmdlet Get-ListDiscoveredOAEntities and it works.
            Now I’m going to test it with BladeSystem MP 1.X where firmware 2.20 is recommended.

  18. Hello,

    I’am trying to monitor my c7000 blade system.
    I’ve followed te steps above but i’am getting these errors:

    The HP Device Monitor Service was unable to authenticate with the device. Please check the credentials for the device and try to discover the device again.
    Authentication error with device 1XX.XXX.XXX.XXX. Make sure device credentials are correct.


    HTTP request error.
    Web Exception status = ProtocolError occurred for http PUSH request: http status = BadRequest.

    My envoirement:

    Server: SCOM 2012 R2 MGMT / DMC / DMS on same server
    Newest HP integration pack
    Blade system C7000
    XML enabled
    Ports are open

      1. Stanislav,

        I use the Users / Authenticating -> Local users -> Privilege Level: Administrator.
        The firmware level is: BladeSystem c7000 Version: 3.30 Apr 19 2011

  19. Thanks for this detailed write up. I’m slightly confused about the SNMP setup.

    I’m running SCOM 2012 R2 with 2 Management servers. I installed the DMC and service on the RMS emulator management server. Configured SNMP service on the same server as you describe. All my HP Blade Enclosures and Virtual Connect hardware is discovered and shows up as healthy in the console.

    However, I’m unable to receive the test SNMP alert from my OA and Virtual Connect. I have a feeling that the SNMP traps are not being sent to the SCOM server. I also noticed that something disabled the SNMP and SNMP Trap service on my SCOM management server?? Any ideas? Should I be installing/configuring SNMP on another box?

    1. Now that I think about it….should the DMC be installed on the RMS/Management server…..and the DMS/SNMP installed elsewhere?

      1. Hi,
        If you are using the Management Servers for monitoring Network Devices it is recommended the DMS/SNMP to be installed on different server than management one. Even if you are not monitoring Network Devices I still recommend using different server. Console you can install anywhere.

      1. I do not and no plan in the future. I do have the NetApp MP installed which may be interfering.

        So the best scenario would be DMC on Management server, DMS/SNMP on any other SCOM agent managed server. Point SNMP alerts from Onboard Admin/Virtual Connect to the DMS/SNMP server.

        I am thinking the DMC needs to be on the Management server as that will link it to the DMS?? How else would the Management servers know the status?

        I appreciate the help here.

  20. Management servers discover the DMS service and get the information from it. DMC is just console for management. There are some snmp listener programs that can be started on the server to see what SNMP ptrapsare received. This is if you are not sure if snmp traps are received. Remember to remove that program after you’ve done that test as might interfere with the Windows SNMP or the SCOM SNMP.

    1. Ok this makes sense now. DMC is just an interface to configure the DMS service on any machine. I was thinking the DMC had to be up and running all the time. Now I understand you can configure it from anywhere.

      I ended up installing DMS on a SCOM managed server and the MP discovered the DMS service running.


  21. Hi,

    Thanks for this guide.

    Please note that with 7.3.2 bundle, connection with DMC to localhost is not possible. At least for me the thing Works only remotely


    1. A follow up on DMC not working Localy

      It actually Works if you run it as Administrator 😉


  22. Hi Stanislav,

    I am trying to access HP Blase chassis with SCOM 2012 R2 but I am stuck at the beginning. Error I am receiving from HP Device Monitor is:

    Web Exception status = ProtocolError occurred for http PUSH request: http status = NotFound.

    SCOM 2012 R2 is virtual machine, I’ve installed HP OneView for SCOM on that server, all services are up and running, I’ve managed to connect to localhost with HP Device Monitor but when I try to add OA, mentioned error is shown. I can access OA through the browser from SCOM server without problems. OA FW is 4.22.

    Do you have any hint what could be the problem?



  23. Just an update, I’ve installed HP BladeSystem Enlosure Monitor Manager and I can connect to the Blade enclosure. On the other hand HP Device Monitor is still reporting above mentioned error….

  24. Hi Stanislav,

    simple check mark solved this issue with HP Device Monitor. I turned on XML Reply and now I can see the enclosure. Now, how can I discover this enclosure in SCOM? Should I just wait or should I do something because nothing is happening in SCOM. I have imported HP Bladesystems Enclosure MP but it is empty.

    Many thanks for your help.



  25. Hi, for some reason SQL Server Broker is disabled so probably that is the reason I can’t discover any Blade enclosure. I will fix that and see if things are working….

  26. Hello Sir,

    Need your assistance on Hardware monitoring.
    We are trying to monitor the HP Proliant hardware for G8 Machines.
    Followed the below steps:
    Follwed the above steps given in site, but still the servers are not discovered.

    Installed and imported management pack on SCOM RMS Test Server
    Installed DMC on a standalone server where SCOM agent was installed (abc machine)
    Installed DMS service a separate machine where the SCOM agent was installed.(efg machine)
    Added EFG machine name on DMC Console.
    Enabled SNMP services on all the three servers (RMS, ABC and EFG)

    Servers are not discovered in SCOM Console, Could you please assist me and let me know did I miss any steps?

    Could you please also let me know what details do we need to give in ADD ONBOARD ADMINISTRATOR.
    Confused at the Credentials part. User name and password.
    shall we give user name and password of the SCOM RMS Machine or any other credentials.

    Please help me and looking forward for your reply.

    Sanjeev Kumar N

    1. Hi Sanjeev,
      First you want to monitor two different hardware components: the physical Proliant server and the enclosures. Both have their own management pack which is configure differently. Take a closer look at my articles again. The Proliant servers can be monitored via two methods SNMP and WMI. My article is how to do it with WMI. Basically you have SCOM agent and HP Insight Management WBEM Providers. When you have these installed on your physical server you will need to import HP ProLiant Server Management Pack in SCOM and configure it with WMI.On monitoring of the enclosures you have another management pack which you mention that is installed. On the Server where DMS service is installed there you need to install, enable and configure SNMP. Configuration is simple you add community string and the IPs of all your HP Onboard administrators. Than you login to all your onboard administrators create the same community string in every one of them. You configure the SNMP on your onboard administrators to send packets where your DMS service is installed. The account that you configure by adding onboard administrator in the DMC console is admin account on your Onboard administrator console. You will need to enable XML Reply (Enclosure settings -> Network Access) for that account. Also make sure that the server where DMS is installed can communicate trough SNMP to all Onboard administrators and that onboard administrator consoles can be opened on that server trough HTTPS(443). All this is in my articles so I suggest to read them carefully again.

      1. Sorry.
        I have some problem( I am doing all the steps in your instructions, but there is no result.
        In log, i see Error:
        HTTP request error.
        Web Exception status = ProtocolError occurred for http PUSH request: http status = NotFound.

        The HP Device Monitor Service was unable to discover the device. Please check the connection and configuration for the device and try to discover the device again. (But XML Reply is Enable)

        Could not discover or identify Ensure the device is up and connected to the network. Ensure the credentials are correct by verifying the community string for SNMP managed devices. Ensure the Insight Management Agents are currently running on in-band server devices. Ensure the Agentless Management is configured properly in the iLO Management Engine for out-of-band server devices.

        From the site SCOM i connect to Hp Enclosure without any problem.
        Credentials in order.

        Hp Enclosure-Firmware 4.21
        Hewlett-Packard BladeSystem Management Pack -
        HP Device Monitor Console -

        Help mi please.

              1. I believe you. I cannot think of any other solution for you. Probably it needs some deeper investigation. You can always open a case to HP. The Management Pack is official supported product by HP. Usually that error appears if you do not have that option enabled as far as I know.

  27. Just a little information I’d like to share. We’ve been going around and trying to monitor the C7000 enclosures (8 of them, actually) and had a very hard time setting everything up the right way. Your article helped a lot though (especially that ruddy XML Reply checkbox…).

    I’ve managed to monitor my enclosures with SCOM 2012 R2 using the MP from HP, but there are some issues with monitoring the VC-10 and the VC-FlexFabric. Sofar I managed to get monitoring working with VC-Flex 4.01 and OA 3.75.

    Our VC-10 using firmware’s 3.51 (OA 3.32) and 3.75 (OA 3.71) don’t work. Even the VC-FlexFabric with firmware 3.75 (OA 3.71) doesn’t seem to work. It may be that it is related to all the different firmware’s we are using or our somewhat messed up SCOM installation. We didn’t have access to a Lab setup, so we did everything for our production enviroment in one go which resulted in semi-finalized installations of Blade Monitor and DMS (which are now all turned off via Services.msc). We now use a SCOM Agent server with DMS installed and that seems to work fine so far.

    So we still face a couple issues. 1. Authentication. The VC-FlexFabric doesn’t allow for more than 3 AD searchdomains, whereas the OA allows for 6. Therefor, we can’t use our regular SCOM account (which is in the 4th container). Besides that we have, as you notice, a lot of different firmwares due to the fact we didn’t buy all the enclosures at once.

    Anyway, this piece of text got way longer than I anticipated, but I’m going to start planning updating all our Firmwares soon and I’ll try to report back to what it will do to our monitoring solution and see in what way it will help getting all our stuff in SCOM 2012 R2!

  28. i just installed enclosure following your guide.but now i dont see the enclosure status at SCOM console, navigating to Monitoring pane –> HP Systems –> HP BladeSystem Enclosures –> Enclosure State:

    Please advise . Thanks

  29. I manage to discover all the enclosure now i have new problem. During testing such poweroff the enclosure i did not see any alert and i notice that the rule is pickup the information from HP device monitor log.

    When i check the log is blank/empty . Try reinstall the service failure to resolve the issues. Please help to get the hp device manager log capturing logs. Thanks

    1. On every enclosures where SNMP is configured you have a button “Send Test Alert”. You can see it in the screenshots. When you press that button SNMP will be send to SCOM and that SNMP will be visible as warning in SCOM console. That is how you test if your enclosure can send alerts.

Leave a Reply

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

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

Facebook photo

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

Connecting to %s

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