This article is the third installment in a series of articles on monitoring HP servers and storage with SCOM. In the first part of this series, I reviewed the integration kit, and supported configuration and other environment considerations. In the second part of this series, I reviewed the steps for installing the HPE SCOM Integration kit. In this article, I will review the steps required for configuring the HPE SCOM Integration kit.
After we’ve installed the SCOM integration kit, and now have the management packs, as seen in the second part of this series, we can now import and configure the monitoring in SCOM.
- In the SCOM console, import one or more management packs.
NOTE: The HPE ProLiant PRO MP is not supported on SCOM 2012 or later versions. There’s no need to install this MP unless you have a pre-2012 iteration of SCOM.
2. Optionally, change the frequency of the discovery rules. By default, the Hewlett Packard Enterprise discovery rules run every four hours. To change the frequency, for the particular rule, create an override that sets IntervalSeconds appropriately.
3. For each DMS instance, add devices to be monitored. This can be done either through the DMC or using the Device Monitor Service (DMS) PowerShell cmdlets to manually add devices and servers. (blog post on this later). The DMC is used to add or remove devices from a DMS.
To open the DMC:
- From the Windows Start menu, click HP Device Monitor Console, or
- From the SCOM console, in the Actions pane, click HP Device Monitor Console.
4. For each DMS monitored device and server, set its SNMP community string and trap destination to the DMS’ IP address.
To add a DMS:
- Click the Add Connection icon.
- Enter the host name or IP address of the Window server where the DMS is located.
- Click Connect.
Upon connecting, you will see various options on the right-side of the console. You can select the actions for adding Onboard Administrator, Agentless Server, Linux or VMware ESX Server, and Virtual Connect Domain.
I’ll select the option for adding Onboard Administrator. Provide the IP Address and credentials to add it.
For illustration, I will also add a Virtual Connect domain, after confirming my Virtual Connect information as seen below.
After adding it to the console, I can see it successfully populates in my DMC.
Open the SCOM console, and navigate to the Monitoring workspace, and look for the HP Systems folder which will contain all of the discoveries as well as agentless discoveries.
We can now see relevant discovery data for HP Systems as shown below.
This concludes the articles on monitoring HP servers. In the next couple of articles in this series, I’ll show you how to monitor HP Storage.
Latest posts by Chiyo Odika (see all)
- Zero Trust and the Azure Firewall service - July 9, 2019
- Making the move to Azure Security Center and Azure Sentinel - July 9, 2019
- Azure Monitor Management solution for RDS, Windows VDI and Citrix - February 28, 2019