<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: SNMP HPE ProLiant Network Interface Sensor

HPE system management tools

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 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.

Sensor Name

Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.

If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include?

Parent Tags

The 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:

• snmphpenetworkinterfacesensor
• 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 ().

Network Interfaces

The name of the network interface that this sensor monitors.

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.

Alignment Errors

The number of alignment errors

Bad Frames Received

The number of bad frames received

Bad Frames Transmitted

The number of bad frames transmitted

Carrier Sense Errors

The number of carrier sense errors

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

Excessive Collisions

The number of excessive collisions

FCS Errors

The number of FCS errors

Frames Too Long

The number of frames that are too long

Good Frames Received

The number of good frames received

Good Frames Transmitted

The number of good frames transmitted

Late Collisions

The number of late collisions

Total

The total traffic

Traffic In

The incoming traffic

This channel is the primary channel by default.

Traffic Out

The outgoing traffic