PRTG Manual: SNMP Traffic Sensor

Interface Number

Select the ports on SNMP devices with multiple interfaces that you want to monitor. PRTG creates one sensor for each port 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.

You can see the connection status of an interface in the respective table column.

You can select interfaces and cancel the selection by clicking Select all connected interfaces, Select all disconnected interfaces, and Deselect all interfaces.

Name for Traffic In Channel

For the standard channel Traffic In, enter the channel name here. The sensor shows it in graphs and tables. You can change this description and the description of all other channels in the channel settings later.

Name for Traffic Out Channel

For the standard channel Traffic Out, enter the channel name here. The sensor shows it in graphs and tables. You can change this description and the description of all other channels in the channel settings later.

Name for Traffic Total Channel

For the standard channel Traffic Total, enter the channel name here. The sensor shows it in graphs and tables. You can change this description and the description of all other channels in the channel settings later.

Sensor Name

Enter a meaningful 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

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:

• bandwidthsensor
• snmptrafficsensor

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

Interface Number

Shows the number and name of the interface in the physical device that this sensor monitors.

PRTG shows this value for reference purposes only. We strongly recommend that you only change it if the Paessler support team explicitly asks you to do so. Wrong usage can result in incorrect monitoring data.

Additional Channels

By default, each SNMP Traffic sensor creates the channels Traffic In, Traffic Out, and Traffic Total. Select additional channels for all interfaces. Click the respective channel names to mark the channels and to monitor their data.

You can choose between the following additional channels:

• Errors in and Errors out: The number of incoming and outgoing packets that could not be delivered because of errors.
• Discards in and Discards out: The number of discarded incoming and outgoing packets even though no errors have been detected.
• Unicast packets in Unicast packets out: The number of unicast packets that have been delivered.
• Non Unicast packets in and Non Unicast packets out (32-bit only): The number of non-unicast packets that have been delivered.
• Multicast packets in and Multicast packets out (64-bit only): The number of delivered packets that were addressed to a multicast address.
• Broadcast packets in and Broadcast packets out (64-bit only): The number of delivered packets that were addressed to a broadcast address
• Unknown Protocols: The number of received packets that were discarded because of an unknown or unsupported protocol.

You cannot delete additional channels later. You can only disable them.

If the sensor shows the Warning status with the message Channels not available, you can disable the affected channels to remove the warning.

Connection Status Handling

Define how PRTG reacts when an interface is operational. An interface that is not operational is, for example, an Ethernet port on a switch with no cable plugged in. This setting is valid for all selected interfaces. Choose between:

• Show down status for all disconnected states: Show the Down status for a disconnected interface. This applies if the ifOperStatus of the interface is not "up".
• Show down status when disconnected, ignore when deactivated: Show the Down status for a disconnected interface only if it is not deliberately deactivated in the configuration. This applies if the ifOperStatus of the interface is not "up" and the ifAdminStatus is "up". So the sensor stays in the Up status when the interface has been deactivated.
• Ignore all disconnected states: Show the Up status.
  Monitoring is discontinued without notice.

Alias Availability

Shows if an alias is available for automatic port name updates.

PRTG shows this value for reference purposes only. We strongly recommend that you only change it if the Paessler support team explicitly asks you to do so. Wrong usage can result in incorrect monitoring data.

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

• Show in and out traffic as positive and negative area graph: Show channels for incoming and outgoing traffic as positive and negative area graph. This visualizes your traffic in a clear way.
  You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings). Manual scaling is not possible if you choose this option.
  You cannot show a positive/negative graph for a channel if you choose to display its data in percent of maximum (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.

Scanning Interval

Select a scanning interval from the dropdown list. The scanning interval determines the amount of time that the sensor waits between two scans. Choose from:

• 30 seconds
• 60 seconds
• 5 minutes
• 10 minutes
• 15 minutes
• 30 minutes
• 1 hour
• 4 hours
• 6 hours
• 12 hours
• 24 hours

You can change the available intervals in the system administration of PRTG Network Monitor.

If a Sensor Query Fails

Select the number of scanning intervals that the sensor has time to reach and to check a device again if a sensor query fails. Depending on the option that you select, the sensor can try to reach and to check a device again several times before the sensor shows the Down status. This can avoid false alarms if the monitored device only has temporary issues. For previous scanning intervals with failed requests, the sensor shows the Warning status. Choose from:

• Set sensor to down immediately: Set the sensor to the Down status immediately after the first request fails.
• Set sensor to warning for 1 interval, then set to down (recommended): Set the sensor to the Warning status after the first request fails. If the second request also fails, the sensor shows the Down status.
• Set sensor to warning for 2 intervals, then set to down: Set the sensor to the Down status only after the third request fails.
• Set sensor to warning for 3 intervals, then set to down: Set the sensor to the Down status only after the fourth request fails.
• Set sensor to warning for 4 intervals, then set to down: Set the sensor to the Down status only after the fifth request fails.
• Set sensor to warning for 5 intervals, then set to down: Set the sensor to the Down status only after the sixth request fails.

Sensors that monitor via Windows Management Instrumentation (WMI) always wait at least one scanning interval before they show the Down status. It is not possible to immediately set a WMI sensor to the Down status, so the first option does not apply to these sensors. All other options can apply.

If you define error limits for a sensor's channels, the sensor immediately shows the Down status. None of the interval options apply.

If a channel uses lookup values, the sensor immediately shows the Down status. None of the interval options apply.

Schedule

Select a schedule from the list. You can use schedules to monitor during a certain time span (days or hours) every week. Choose from:

• None
• Saturdays
• Sundays
• Weekdays
• Weekdays Eight-To-Eight (08:00 - 20:00)
• Weekdays Nights (17:00 - 09:00)
• Weekdays Nights (20:00 - 08:00)
• Weekdays Nine-To-Five (09:00 - 17:00)
• Weekends

You can create schedules, edit schedules, or pause monitoring for a specific time span. For more information, see section Schedules.

Maintenance Window

Select if you want to set up a one-time maintenance window. During a maintenance window, monitoring stops for the selected object and all child objects. They show the Paused status instead. Choose between:

• Do not set up a one-time maintenance window: Do not set up a one-time maintenance window. Monitoring is always active.
• Set up a one-time maintenance window: Set up a one-time maintenance window and pause monitoring. You can define a time span for the pause below.

To terminate an active maintenance window before the defined end date, change the time entry in Maintenance Ends to a date in the past.

Maintenance Begins

This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the start date and time of the one-time maintenance window.

Maintenance Ends

This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the end date and time of the one-time maintenance window.

Dependency Type

Select a dependency type. You can use dependencies to pause monitoring for an object depending on the status of a different object. You can choose from:

• Use parent: Use the dependency type of the parent object.
• Select a sensor: Use the dependency type of the parent object. Additionally, pause the current object if a specific sensor is in the Down status or in the Paused status because of another dependency.

• Master sensor for parent: Make this sensor the master object for its parent device. The sensor influences the behavior of its parent device: If the sensor is in the Down status, the device is paused. For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor is paused if the parent group is paused by another dependency.

To test your dependencies, select Simulate Error Status from the context menu of an object that other objects depend on. A few seconds later, all dependent objects are paused. You can check all dependencies under Devices | Dependencies in the main menu bar.

Dependency

This setting is only visible if you enable Select a sensor above. Click and use the object selector to select a sensor on which the current object will depend.

Dependency Delay (Sec.)

This setting is only visible if you select Select a sensor above. Define a time span in seconds for the dependency delay.

After the master sensor for this dependency returns to the Up status, PRTG additionally delays the monitoring of the dependent objects by the time span you define. This can prevent false alarms, for example, after a server restart or to give systems more time for all services to start. Enter an integer value.

This setting is not available if you set this sensor to Use parent or to be the Master sensor for parent. In this case, define delays in the parent device settings or in its parent group settings.

User Group Access

Define the user groups that have access to the sensor. You see a table with user groups and group access rights. The table contains all user groups in your setup. For each user group, you can choose from the following group access rights:

• Inherited: Inherit the access rights settings of the parent object.
• No access: Users in this user group cannot see or edit the sensor. The sensor neither shows up in lists nor in the device tree.
• Read access: Users in this group can see the sensor and view its monitoring results. They cannot edit any settings.
• Write access: Users in this group can see the sensor, view its monitoring results, and edit its settings. They cannot edit its access rights settings.
• Full access: Users in this group can see the sensor, view its monitoring results, edit its settings, and edit its access rights settings.

For more details on access rights, see section Access Rights Management.

Channel Unit Types

For each type of channel, select the unit in which PRTG displays the data. If you define this setting on probe, group, or device level, you can inherit these settings to all sensors underneath. You can set units for the following channel types (if available):

• Bandwidth
• Memory
• Disk
• File
• Custom

Custom channel types are only available on sensor level.

Discards In

The number of incoming discards per second

Discards Out

The number of outgoing discards 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 in percent.

Errors In

The number of incoming errors per second

Errors Out

The number of outgoing errors per second

Non-Unicast In

The number of incoming non-unicast packets per second

Non-Unicast Out

The number of outgoing non-unicast packets per second

Traffic In

The incoming traffic in bytes per second

Traffic Out

The outgoing traffic in bytes per second

Traffic Total

The total traffic in bytes per second

This channel is the primary channel by default.

Unicast In

The number of incoming unicast packets per second

Unicast Out

The number of outgoing unicast packets per second

Unknown Protocols In

The number of incoming, unknown protocols per second