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

4 More about the HP Device Monitor
This chapter provides supplemental information about the operation of the HP Device Monitor.
HP Device Monitor architecture
The DMS provides a communication link between non-Windows devices that are managed from
within Microsoft System Center Operations Manager (SCOM). The Device Monitor Service is built
on HP Common Services, which provides the underlying monitoring of the managed devices. On
ProLiant servers running Windows, the HP Insight Management Agents (SNMP) or HP Insight
Management WBEM Providers communicate directly to the HP ProLiant Server management pack
on the SCOM console via a Microsoft SCOM agent that is loaded locally on each managed node.
Because non-Windows devices such as HP BladeSystem enclosures, ILO Management Engines,
Linux servers, and VMware servers cannot have Windows-based SCOM agents loaded locally,
they must communicate directly with the DMS.
Figure 2 (page 20) shows the communication paths.
Figure 2 HP Device Monitor communication paths
The DMS can run on any Windows server managed by SCOM (either a physical or a virtual
machine). The DMS uses the SCOM agent of the managed node on which it is installed to
communicate with the HP management packs on the SCOM console.
The DMC is an application that communicates directly with instances of the DMS, providing the
capability to add or remove non-Windows devices. Non-Windows devices must be registered with
an instance of the DMS before they can be managed in the SCOM console. As shown in
Figure 3
(page 21) , it is possible to run multiple DMS instances. The DMC can communicate with all of the
instances simultaneously.
NOTE: Adding the same managed device to multiple DMS instances is not recommended.
20 More about the HP Device Monitor