This is the fourth article in a series of articles on how to monitor HP servers and storage with System Center Operations Manager (OpsMgr). 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 the third article in this series, I reviewed the steps required for configuring the HPE SCOM Integration kit. In this article, I’ll review the HP Storage Management Pack features, and required configurations for the SNMP event delivery method. This article is based on the HP Storage Management Pack v4.2.1.
The HP Storage Management Packs enhance your management capabilities, providing an integrated view of your datacenter infrastructure. Each pack simplifies management by seamlessly integrating predefined discovery and state monitoring policies, event processing rules and tasks with Microsoft Systems Center Operations Manager. This management pack is designed to receive alerts, events, topology, capacity, and health information from the HP Storage portfolio.
Key Benefits
The HP Storage Management Pack integrates hardware resource management into Microsoft System Center Operation Manager and provides the following functionality:
- Monitor HP Storage Hardware in OpsMgr
- Predefined rules to process and clearly display events and alerts for HP storage hardware in the Operations Manager Consoles
- Automated Installation and Discovery
- Fully scripted installation that creates HP specific groups and copies HP rules, scripts, views, tasks and knowledge base data to the OpsMgr database
- Discover and manage multiple HP Storage products and management environments
- Compatibility with HP Resource Management Tools
The 4.2.1 version of the HP Storage Management pack supports the following:
- Monitoring of HP 3PAR File Persona Alerts
- Enhanced health dashboard for HP 3PAR StoreServ Systems
- HP 3PAR Inform OS 3.2.2
- HP StoreVirtual LeftHand OS 12.5
Supported Devices
The HP Storage Management Pack supports the following Storage Devices:
- HP Storage ESL E-Series, EML E-Series, ESL 6000/9000/12000, and MSL Series
- HP XP 9000 Storage
- HP EVA P6000 Storage
- HP MSA Storage
- HP E5000 Messaging System
- HP StoreEasy 5000 Storage
- HP 3PAR StoreServ Storage
- HP StoreOnce Backup System
- HP StoreEasy 1000 and HP StoreEasy 3000 Storage
- HP StoreVirtual Storage (both Appliance and VSA)
- HP 3PAR StoreServ File Controller
- HP 3PAR StoreServ 20000 series (Partially)
System Requirements
The following Operating Systems are supported for the Storage Management Pack installation on the OpsMgr Server.
The HP Storage Management Pack supports the following event delivery methods.
While event delivery through Web-based Enterprise Services (WEBES) is fully supported as shown above, this article will focus on event delivery through SNMP.
Using SNMP
To configure events to flow from the Storage Device Manager to System Center, you will need one to three systems. Primarily you will need to plan for the deployment of the SNMP Collection Point, assuming that you already have a OpsMgr deployed.
NOTE: While the collection point role can be installed on a server where the OpsMgr agent is deployed, this role can also be installed on a OpsMgr server, provided that the server is not part of a Network Monitoring Resource Pool/ Network Discovery Server. This is because if the server is part of the Network Resource Pool/ Network Discovery Server, the 162 port is utilized by SCOM instead of the SNMP Trap service, and so alerts are not captured.
This concludes this article on the supported configurations for deploying the HP Storage Management Pack in System Center. In the next article, I will walk through the discovery and monitoring of a HP StoreVirtual Storage System with the HP Storage Management Pack.
Cheers!
Latest posts by Chiyo Odika (see all)
- Replicate Proximity Placement Group workloads in Azure - January 13, 2021
- Azure NetApp Files (ANF) – Deploy with JSON - October 9, 2020
- Addressing Critical ZeroLogon Vulnerability CVE-2020-1472 - September 26, 2020