<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: SNMP HPE ProLiant Memory Controller Sensor

HPE system management tools

For Gen10 servers: This sensor requires HPE Agentless Management and the HPE Agentless Management Service on the target system.

For Gen10 servers: Use the HPE Integrated Lights Out (iLO) interface as the parent device.

For Gen9 servers or earlier: This sensor requires HPE Insight Management Agents and HPE Insight Management WBEM Providers on the target system.

For Gen9 servers or earlier, this sensor requires a specific HPE system management tool to be installed on the target system to report data via SNMP: HPE Insight Management Agents. To receive SNMP data from redundant array of independent disks (RAID) controllers, the sensor also requires HPE Insight Management Agents. For Gen10 servers, this sensor no longer requires HPE system management tools. Instead, the sensor requires the HPE Agentless Management Service to be installed on the target system.

For more information and download links, see the Knowledge Base: Monitor HP ProLiant via SNMP?

For Gen9 servers or earlier, some of the HPE object identifiers (OID) that this sensor uses are only accessible via the iLO interface. If this sensor throws an error that it cannot find "such device types", create a device that points to the address of the HPE iLO interface (if available) and add the sensor to this device. We recommend that you use the Agentless Management feature with configured SNMP. You can set this up in the iLO configuration interface under Administration | Management | SNMP Settings. For Gen10 servers, use the HPE iLO interface as parent device for this sensor.

iLO versions

This sensor supports iLO as of iLO 3. We recommend that you use at least iLO 4.

IPv6

This sensor supports IPv6.

Performance impact

This sensor has a very low performance impact.

Lookups

This sensor uses lookups to determine the status values of one or more channels.

Modules

If modules are inserted at a later point, you must add this sensor anew.

Knowledge Base

Knowledge Base: Which lookup values are supported by the SNMP HPE ProLiant Memory Controller sensor?

Controller

The name of the controller that this sensor monitors.

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, PRTG displays the last value of the primary channel below the sensor's name. The available options depend on what channels are available for this sensor.

You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab.

Graph Type

Define how this sensor shows different channels:

• Show channels independently (default): Show a graph for each channel.
• Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
  You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This setting is only visible if you select Stack channels on top of each other above.

Select a unit from the list. PRTG stacks all channels with this unit on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.

Controller Condition

The controller condition

• Up status: OK
• Warning status: Degraded
• Down status: Failed
• Unknown status: Other

Controller Error Status

The controller error status

• Up status: Advanced Ecc, Lock Step, Memory Raid, Mirrored, No Error, OnlineSpare
• Down status: Bus Error, Config Error, Dimm Ecc Error, Lock Step Error, Mirrored Dimm Error, Power Error, Raid Dimm Error, Unlock Error
• Unknown status: Other

This channel is the primary channel by default.

Downtime

In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status.

Module [#] Condition

The module condition

• Up status: OK
• Down status: Degraded, Failed
• Unknown status: Other

Module [#] Status

The module status

• Up status: Add, Good, Present
• Warning status: Not Present, Upgrade
• Down status: Bad Config, Degraded, Does Not Match, Missing, Not Supported
• Unknown status: Other