HP OneView for Microsoft System Center - Manual (Page 22)

5 Device monitor performance and scalability guidelines
The DMS acts as a proxy to communicate between the HP Management Packs on the SCOM Server
and the non-Windows monitored devices (BladeSystem Onboard Administrator, Virtual Connect
Domains, and supported Linux, VMware, and Agentless servers). The DMS requires system and
network resources that are shared with an Operations Manager server or other applications on
the system where it is configured. As the number of monitored devices increases, resource utilization
by the DMS may also increase.
This information describes performance characteristics for the DMS and example configurations.
Monitoring process overview
A single DMS instance monitors multiple devices simultaneously. Each monitored device must be
registered with the DMS instance through the Device Monitor Console (DMC) or PowerShell cmdlets.
The following phases are involved in the monitoring process:
•
Phase 1. Connection
Establishes a connection to the device
•
Phase 2. Data collection
Collects inventory and state information of a device
•
Phase 3. Monitoring
Monitors for changes to inventory or state information of a device
•
Phase 4. Data recollection
Re-collects updated inventory and state information of a device as reported during the
monitoring phase (phase 3).
The connection and data collection phases occur once in a connection. The data collection phase
is the busiest phase and uses a significant amount of system and network resources. After the data
collection is complete, the management packs can access all enclosure data to produce inventory
and state information. The DMS spends most of the time in the monitoring phase to detect any
information change to the monitored device. If a change is found, the data re-collection starts and
collects partial data only where a change is reported. After the data re-collection is complete, the
DMS continues the monitoring phase.
SNMP trap monitoring is performed simultaneously with the above phases. SNMP trap monitoring
establishes communication to the SNMP trap service and is not a factor in performance
characteristics unless a significant number of SNMP traps are generated into the network.
Factors influencing performance characteristics of the Monitor Service
•
Number of registered devices
The connection, data collection, and monitoring phases are processed on a per-device basis.
Adding more monitored devices (enclosures, Linux, VMware, Virtual Connect Domains, or
Agentless servers) to a DMS increases system and network utilization.
•
Rate of configuration changes and error events to enclosures
Any configuration change of a monitored device triggers the data recollection phase. If a
failing component continually changes between healthy and degraded states, every state
22 Device monitor performance and scalability guidelines