locked
HP Management pack issue RRS feed

  • Question

  • We have a SCOM 2012in production and we are setting up SCOM 2019 infrastructure. The SCOM 2019 infrastructure is not giving us HP alerts, management wants the HP alerts to work.

    SCOM 2012 has the pack versions:

    SCOM 2019 has the pack versions:

    SCOM 2019 is not giving us any HP alerts and the agents is all on HP machines, we have read the MGMT pack documentation and it sounds like a middle man device needs to be stood up for the HP events, this will not be approved in our environment…. Does anyone have a solution for HP management packs to work in SCOM 2019 without adding middle man devices?


    The question has also been asked here:

    https://h30434.www3.hp.com/t5/HP-Workspace/SCOM-2019-HPE-Management-pack-not-giving-alerts/td-p/7702083

    Friday, July 24, 2020 8:22 PM

Answers

  • Use an older version of the mp. We have 1.80 or so in our 2019 environment and it works fine. You just have to ensure if you use the wmi one that Webem gets installed on the hp hardware. Also use one or the other you have both the wmi and snmp. I’ve always used the wmi version. We are not using any hp map that requires you to stand up another component of hp. That product is not easy to deploy and I am not sure that it’s free either.

    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

    Saturday, July 25, 2020 3:42 AM
  • Ok, just be careful.

    We are using hyper-v.  I can't remember when the webem piece needs to be installed, but I know in our development process, there was a certain step when to install webem on the physical servers that host the vms.  

    Having said that, once the webem piece is installed on the hp hardware, import the wmi version the the hp MP and that's pretty much it.

    I will say, when you go to the HP state view in the MP, you have to customize it because it shows only the hostname.  Really annoying, and something that you cannot modify using the SCOM 2019 web console view.


    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

    Sunday, July 26, 2020 2:45 AM
  • This is a new and separate environment. If Webem is already there then no need to reinstall.

    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

    Sunday, July 26, 2020 3:41 AM
  • The WMI MP requires webem installed on the hardware, and will not require you to configure SNMP.  If you use SNMP, you have to configure it on the servers where agents are deployed and the management servers.  I don't recommend using SNMP, it's not reliable.

    Have you looked at the guide for the HP mp?  I would validate that the webem components have been installed on a HP server, and work from there to start troubleshooting.


    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

    Monday, July 27, 2020 9:17 PM

All replies

  • Hello,

    I'm not using the HP management pack, but it seems that now HP recommends to use HPE OneView MP instead on this proliant MP:

    https://myenterpriselicense.hpe.com/cwp-ui/free-software/HPSCOMMP-P

    Maybe it works better on SCOM 2019, just a suggestion :)

    Friday, July 24, 2020 10:22 PM
  • Correct the new Management packs appear to require a second device (middle man) which has hp one view on it for SCOM to work properly with HP... This is the middle man device and setup that will not be allowed or thought of... Thus why I am hoping someone out there has a work around
    Friday, July 24, 2020 10:40 PM
  • Ok i understand ;)

    I dont have a SCOM 2019 server yet, so I can not try this MP. Hopefully someone will be able to find a workaround. Good luck!

    Friday, July 24, 2020 10:59 PM
  • Use an older version of the mp. We have 1.80 or so in our 2019 environment and it works fine. You just have to ensure if you use the wmi one that Webem gets installed on the hp hardware. Also use one or the other you have both the wmi and snmp. I’ve always used the wmi version. We are not using any hp map that requires you to stand up another component of hp. That product is not easy to deploy and I am not sure that it’s free either.

    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

    Saturday, July 25, 2020 3:42 AM
  • I will do that, is there anything else I will need to do once I add the MP's? do I need to enable the pack or configure settings? Once the packs are installed will it start working automatically?
    Sunday, July 26, 2020 2:39 AM
  • Ok, just be careful.

    We are using hyper-v.  I can't remember when the webem piece needs to be installed, but I know in our development process, there was a certain step when to install webem on the physical servers that host the vms.  

    Having said that, once the webem piece is installed on the hp hardware, import the wmi version the the hp MP and that's pretty much it.

    I will say, when you go to the HP state view in the MP, you have to customize it because it shows only the hostname.  Really annoying, and something that you cannot modify using the SCOM 2019 web console view.


    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

    Sunday, July 26, 2020 2:45 AM
  • Thanks for the information... The HP servers are working within the scom 2012 environment, the goal is to remove the scom 2012 agents and install the scom 2019 agents, the webem component is already installed.

    When you moved from your previous version to scom 2019 did you have to change the webem settings or reinstall it?

    Sunday, July 26, 2020 2:56 AM
  • This is a new and separate environment. If Webem is already there then no need to reinstall.

    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

    Sunday, July 26, 2020 3:41 AM
  • So when we install the scom 2019 agents it should detect the HP servers automatically?
    Sunday, July 26, 2020 3:47 AM
  • Yes. That’s right.

    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

    Sunday, July 26, 2020 3:55 AM
  • You might find info from this thread useful (especially the link to Stoyan's blog)

    https://social.technet.microsoft.com/Forums/systemcenter/en-US/b0e41609-4837-45c0-bd92-43622fe63777/hardware-monitoring-performed-through-the-scom-agent-installed-in-the-windows-os?forum=operationsmanagergeneral

    Stoyan's blog

    https://www.pohn.ch/system-center-operations-manager-scom-monitoring-hpe-proliant-gen10-servers/

    And this HPE white paper

    https://support.hpe.com/hpesc/public/docDisplay?docId=c04347838

    Thanks,

    Doug

    Monday, July 27, 2020 2:27 PM
  • Thanks for the information.

    I have installed the MP and configured the setup within our 2019 SCOM to match our 2012 SCOM and  none of the HP hardware is reporting all the groups in the "group state" location say not monitored.

    I have verified that the servers have the same SNMP service trap setting with read only and in OPS manager it looks correct, why won't any of the HP hardware report in?

    I think we are using the WMI method not the SNMP method
    Monday, July 27, 2020 7:12 PM
  • The WMI MP requires webem installed on the hardware, and will not require you to configure SNMP.  If you use SNMP, you have to configure it on the servers where agents are deployed and the management servers.  I don't recommend using SNMP, it's not reliable.

    Have you looked at the guide for the HP mp?  I would validate that the webem components have been installed on a HP server, and work from there to start troubleshooting.


    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

    Monday, July 27, 2020 9:17 PM
  • The 2019 servers do not have the HP WEBM provider installed and this is because HP has not created a package for server 2019, we have to re-evaluate everything
    Tuesday, July 28, 2020 3:46 PM
  • If it is HPE ProLiant Gen10 servers, then there are no SNMP agents or WBEM providers available (it's not a Server 2019 thing, they're not available for any OS).  If it is Gen 9 or earlier, then you can use the regular HPE MP (based on SNMP or WBEM)

    The only way to get the hardware monitoring and alerts with the HPE MP for Gen10 servers is by using OneView.

    Thanks,

    Doug

    Tuesday, July 28, 2020 4:53 PM