PRTG Manual: SNMP HPE ProLiant Network Interface Sensor
The SNMP HPE ProLiant Network Interface sensor monitors a network interface in an HPE server via the Simple Network Management Protocol (SNMP).
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
▪Dutch: SNMP HPE ProLiant Netwerkinterface
▪French: HPE ProLiant interface réseau (SNMP)
▪German: SNMP HPE ProLiant Netzwerkschnittstelle
▪Japanese: SNMP HPE ProLiant ネットワークインターフェース
▪Portuguese: Interface de rede HPE ProLiant (SNMP)
▪Russian: Сетевой интерфейс HPE ProLiant по SNMP
▪Simplified Chinese: SNMP HPE ProLiant 网络接口
▪Spanish: Interfaz de red HPE ProLiant (SNMP)
▪For Gen9 servers or earlier: This sensor requires HPE Insight Management Agents and HPE Insight Management WBEM Providers to be installed on the target device.
▪For Gen10 servers: This sensor requires HPE Agentless Management and the HPE Agentless Management Service to be installed on the target device.
▪For Gen10 servers: Use the HPE Integrated Lights Out (iLO) interface as the parent device for this sensor.
▪During sensor creation, the status of each available network interface is shown. If this status is Link Failure, it is still possible to add a sensor for the respective interface. Though, most likely the sensor for this interface does not work correctly. The error message in this case is "No Such Name (SNMP error # 2)".
▪This sensor supports monitoring iLO as of iLO version 3. We recommend that you use at least iLO 4.
▪This sensor supports the IPv6 protocol.
▪This sensor has a low performance impact.
Requirement |
Description |
---|---|
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.
|
The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the settings that are required to create the sensor. You can change nearly all settings on the sensor's Settings tab after creation.
The settings that you select in the Add Sensor dialog are valid for all sensors that you create when you finish the dialog.
HPE ProLiant Network Interface Settings
Setting |
Description |
---|---|
Network Interface |
Select the network interfaces that you want to monitor. PRTG creates one sensor for each interface that you select.
|
Click the Settings tab of a sensor to change its settings.
Setting |
Description |
---|---|
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.
|
Parent Tags |
Shows tags that the sensor inherits from its parent device, parent group, and parent probe.
|
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.
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 ( |
Usually, a sensor connects to the IP Address/DNS Name of the parent device. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings.
HPE ProLiant Network Interface Settings
Setting |
Description |
---|---|
Network Interfaces |
Shows the name of the network interface that this sensor monitors.
|
Setting |
Description |
---|---|
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.
|
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. |
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. |
By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
For more information, see section Root Group Settings, section Access Rights.
Which channel units are available depends on the sensor type and the available parameters. If no configurable channels are available, this field shows No configurable channels.
For more information, see section Root Group Settings, section Channel Unit Configuration.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Alignment Errors |
The number of alignment errors per second |
Bad Frames Received |
The number of bad frames received per second |
Bad Frames Transmitted |
The number of bad frames transmitted per second |
Carrier Sense Errors |
The number of carrier sense errors per second |
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 per second |
FCS Errors |
The number of Frame Check Sequence (FCS) errors per second |
Frames Too Long |
The number of frames that are too long per second |
Good Frames Received |
The number of good frames received per second |
Good Frames Transmitted |
The number of good frames transmitted per second |
Late Collisions |
The number of late collisions per second |
Total |
The total traffic in bytes per second |
Traffic In |
The incoming traffic
|
Traffic Out |
The outgoing traffic |
KNOWLEDGE BASE
Monitor HP ProLiant via SNMP?
▪https://kb.paessler.com/en/topic/33133
What security features does PRTG include?
▪https://kb.paessler.com/en/topic/61108
My SNMP sensors don’t work. What can I do?