<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: SNMP SonicWall VPN Traffic Sensor

The SNMP SonicWall VPN Traffic sensor monitors the traffic of an Internet Protocol Security (IPsec) VPN on a SonicWall Network Security Appliance (NSA) via the Simple Network Management Protocol (SNMP).

SNMP SonicWall VPN Traffic Sensor

SNMP SonicWall VPN Traffic Sensor

i_square_cyanFor a detailed list and descriptions of the channels that this sensor can show, see section Channel List.

Sensor in Other Languages

  • Dutch: SNMP SonicWall VPN Verkeer
  • French: SonicWall trafic VPN (SNMP)
  • German: SNMP SonicWall VPN-Datenverkehr
  • Japanese: SNMP SonicWall VPN トラフィック
  • Portuguese: Tráfego de VPN SonicWall (SNMP)
  • Russian: Трафик VPN SonicWall по SNMP
  • Simplified Chinese: SNMP SonicWall VPN 流量
  • Spanish: Tráfico VPN SonicWall (SNMP)

Remarks

  • This sensor supports IPv6.
  • This sensor has a very low performance impact.

Add Sensor

Setting

Description

Connection

Select the connections that you want to monitor. PRTG creates one sensor for each connection that you select.

Basic Sensor Settings

Basic Sensor Settings

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

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

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

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

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

  • snmpsonicwallvpntrafficsensor
  • traffic

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 (i_priority_1) to the highest priority (i_priority_5).

SonicWall VPN Specific

SonicWall VPN Specific

SonicWall VPN Specific

Setting

Description

Security Policy

The security policy of the connection that this sensor monitors.

Remote IP Address

The remote IP address of the connection that this sensor monitors.

Source IP Addresses

The source IP addresses of the connection that this sensor monitors.

Destination IP Addresses

The destination IP addresses of the connection that this sensor monitors.

Index

The index of the connection that this sensor monitors.

Identification Method

Define how you want to identify the connection that you want to monitor:

  • Index: Every connection has a unique index. This is the safest method to identify your connection. If the connection is lost and reconnected, it receives a new index.
  • Remote IP address: If the target of the VPN always has the same IP address, you can use this IP address to identify the connection.
  • Security policy name: If you use a different security policy for every VPN, you can use its name to identify the connection.
  • Remote IP address and security policy name: You can also combine both identification methods.
  • Remote IP address, security policy name, and IP address ranges: If you use separate connections for specific IP address ranges, identify the connection by remote IP address, security policy name, and IP address ranges.
  • IP address ranges: Use IP address ranges only to identify the connection.

i_round_blueThe sensor always uses the first connection that it finds that matches all criteria.

i_round_blueYou cannot change this value after sensor creation.

Sensor Display

Sensor Display

Sensor Display

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.

i_round_blueYou can set a different primary channel later by clicking b_channel_primary 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.
    i_round_redYou 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. 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.

Inherited Settings

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 b_inherited_enabled under the corresponding setting name to disable the inheritance and to display its options.

i_square_cyanFor more information, see section Inheritance of Settings.

Scanning Interval

Scanning Interval

Scanning Interval

i_square_cyanFor more information, see section Root Group Settings, section Scanning Interval.

Schedules, Dependencies, and Maintenance Window

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

Schedules, Dependencies, and Maintenance Window

Schedules, Dependencies, and Maintenance Window

i_square_cyanFor more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.

Access Rights

Access Rights

Access Rights

i_square_cyanFor more information, see section Root Group Settings, section Access Rights.

Channel Unit Configuration

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

Channel Unit Configuration

Channel Unit Configuration

i_square_cyanFor more information, see section Root Group Settings, section Channel Unit Configuration.

Channel List

i_round_blueWhich channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.

Channel

Description

Decrypted Packets

The number of decrypted packets

Decrypted Transmissions

The decrypted transmissions

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

Encrypted Packets

The number of encrypted packets

i_round_blueThis channel is the primary channel by default.

Encrypted Transmissions

The encrypted transmissions

Fragmented Packets In

The number of incoming fragmented packets

Fragmented Packets Out

The number of outgoing fragmented packets

More

i_square_blueKNOWLEDGE BASE

Why does PRTG write error messages into my SonicWall log?

What security features does PRTG include?

My SNMP sensors don’t work. What can I do?