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

change triggers the data re-collection phase and causes additional load to the DMS while the
information updates.
•
Connection recovery
The DMS uses heartbeat monitoring to recover the connection if it is disrupted for 60 seconds
or longer. If no heartbeat is detected for a connection, the current connection disconnects and
a new connection starts. If there is a network infrastructure issue that causes instability between
the DMS and the monitored device, the DMS will be busy re-establishing connection to the
monitored device until it succeeds.
Best practices based on these factors
•
Move the DMS to non-Operations Manager servers, except when monitoring the maximum
50 BladeSystem enclosures or 50 VC Domains.
If the Operations Manager server is highly utilized, you may not want the DMS to share that
same resource. In most situations we recommend you move the DMS to any Windows managed
node to free up resource sharing from the Operations Manager server. However, there can
be SCOM agent discovery data size limitations encountered when the DMS is not installed
on the SCOM server. In some cases, a remote DMS will be able to discover and monitor up
to 50 enclosures or 50 VC Domains, but the SCOM agent will not be able to send all the
data over to the SCOM server for discovery in SCOM. Due to this limitation, when monitoring
the maximum 50 BladeSystem enclosures or 50 VC Domains, install the Device Monitor Service
locally on the Operations Manager server.
•
Use multiple instances of the DMS
Multiple DMS instances can be deployed to multiple managed nodes in an Operations Manager
domain to divide and reduce the monitoring resource requirements per DMS instance.
•
Run the DMS instances in a Hyper-V cluster for high availability
The DMS can be installed on a Hyper-V virtual machine. If this is part of a Hyper-V cluster, it
provides failover service for the virtual machine. The DMS is not cluster aware, and HP does
not recommend running it as a clustered service on its own.
Recommended system requirements
The DMS system requirements can vary based on many factors in the managed environment,
including the number of managed devices. A single instance of the DMS can manage a maximum
of 50 BladeSystem enclosures or 50 Virtual Connect Domains, and 250 ProLiant servers (per server
type) as well as exist on a physical server or VM. The following describes a minimum system
configuration suggested for managing the maximum number of supported devices:
•
Hyper-V VM with HP Device Monitor Service installed on the VM:
4 Virtual Processors @ 2.3 GHz ◦
◦ 8 GB memory
◦ 80 GB total disk space
◦ 1 GbE network adapter
Best practices based on these factors 23