Submit a ticketCall us
Home > Success Center > Server & Application Monitor (SAM) > SAM 6.6.1 Administrator Guide > Additional SAM technology requirements > Asset inventory and hardware health monitoring requirements in SAM

Asset inventory and hardware health monitoring requirements in SAM

Updated April 10, 2018

Asset inventory data collection can be enabled for both physical and virtual assets and functions independently of hardware health monitoring. This means you do not need to have hardware health monitoring enabled to have inventory data collected and displayed.

The following hardware supports Asset Inventory data collection:

  • Dell servers with OpenManage Server Administrator Managed Node 7.2 or later.
  • HP servers with HP System Insight Manager (SIM) 6.2 or later.

For HPE ProLiant Gen10 Servers, use SIM 8.0 or later.

  • IBM server with IBM Director (Common Agent, 6.3 or later).
  • Additional hardware not listed here may be supported with a limited amount of information returned from the polling process.

The Asset Inventory feature supports the following operating systems and protocols and does not count against your SAM component monitor license. Additionally, these nodes must be managed by SAM to enable collection of Asset Inventory data:

Operating System






AIX (v7 and higher)


VMware ESX/ESXi v4.x and v5.x

  • CIM
  • VMware API
  • SNMP for VMware nodes not polled via CIM or the VMware API

VMware API for ESX/ESXi hosts polled via vCenter.


Third-party software required for Asset Inventory information







Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Last modified