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

HPE system management tools

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

For more details 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.

Controllers

Select the memory controllers that you want to monitor. PRTG creates one sensor for each memory controller that you select.

Enable check boxes in front of the respective lines to select the items. Use the check box in the table header to select all items or to cancel the selection. In large tables, use the search function in the upper-right corner.

Sensor Name

Enter a name to identify the sensor.

Parent Tags

Shows tags that the sensor inherits from its parent device, parent group, and parent probe.

This setting is for your information only. You cannot change it.

Tags

Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.

It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

For performance reasons, it can take some minutes until you can filter for new tags that you added.

The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:

• snmphpememorycontrollersensor
• memorycontroller
• snmphpe
• hpe

Priority

Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority () to the highest priority ().

Controller

Shows the name of the controller that this sensor monitors.

PRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed 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 different channels are shown for this sensor:

• 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 enable Stack channels on top of each other as Graph Type. Select a unit from the list. All channels with this unit are stacked 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 condition of the controller

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

Controller Error Status

The error status of the controller

• 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 in percent.

Module [#] Condition

The condition of the module

• Up status: OK

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

Module [#] Status

The status of the module

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