PRTG Manual: Cisco IP SLA Sensor

The Cisco IP SLA sensor monitors Voice over IP (VoIP) network parameters using IP service level agreements (SLA) from Cisco via the Simple Network Management Protocol (SNMP).

Cisco IP SLA Sensor

Cisco IP SLA 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: Cisco IP SLA
  • French: Cisco IP SLA
  • German: Cisco IP SLA
  • Japanese: Cisco IP SLA
  • Portuguese: Cisco IP SLA
  • Russian: Cisco IP SLA
  • Simplified Chinese: Cisco IP SLA
  • Spanish: Cisco IP SLA

Remarks

Consider the following remarks and requirements for this sensor:

Remark

Description

IPv4

This sensor only supports IPv4.

Performance impact

This sensor has a low performance impact.

Lookups

This sensor uses lookups to determine the status values of one or more channels.

Object identifiers (OID)

If the object identifiers (OID) that this sensor uses are not available on the target device, the sensor shows the error message: No such object (SNMP error # 222). If this occurs, open the SNMP Compatibility Options setting of the parent device or group and set the Request Mode to Use single get.

Sensor creation

If there is a very large number of IP SLAs available during sensor creation, we recommend that you limit the result set by using the Start Interface Index and End Interface Index options in the SNMP Compatibility Options setting of the parent device or group.

Basic Sensor Settings

Basic Sensor Settings

Basic Sensor Settings

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

  • ipslasensor

i_square_cyanFor more information about basic sensor settings, see section Sensor Settings.

IP SLA Specific

IP SLA Specific

IP SLA Specific

Setting

Description

ID

The ID of the SLA that this sensor monitors.

This sensor can support the following operations with the specified type IDs:

  • echo (1)
  • pathEcho (2)
  • fileIO (3)
  • script (4)
  • udpEcho (5)
  • tcpConnect (6)
  • http (7)
  • dns (8)
  • jitter (9)
  • dlsw (10)
  • dhcp (11)
  • ftp (12)
  • icmp-jitter (16)
  • path-jitter (23)

i_round_blueThe numbers are the IDs of the SLA types as reported by the target device. PRTG translates them into the corresponding strings. These IDs are independent of the IDs that you see in the Add Sensor dialog. If the target device returns other values, this sensor shows an error message that says that it cannot find the type.

i_round_bluePacket loss values are summarized but have no explicit channel for source-destination or destination-source values.

Type

The type of the SLA that this sensor monitors.

Name (Tag)

The name of the SLA that this sensor monitors.

Owner

The owner of the SLA that this sensor monitors.

Frequency

The frequency of the SLA that this sensor monitors.

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, PRTG displays the last value of the primary channel 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 this sensor shows different channels:

  • 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. PRTG stacks all channels with this unit 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.

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

Avg. Jitter

The average jitter

Avg. Jitter Destination - Source

The average jitter between destination and source

Avg. Jitter Source - Destination

The average jitter between source and destination

Avg. Latency Destination - Source

The average latency between destination and source

Avg. Latency Source - Destination

The average latency between source and destination

Average Round Trip Time (RTT)

The average RTT

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

ICPIF

The ICPIF

Late Packets

The number of late packets

Max. Latency Destination - Source

The maximum latency between destination and source

Max. Latency Source - Destination

The maximum latency between source and destination

Max. RTT

The maximum RTT

Min. Latency Destination - Source

The minimum latency between destination and source

Min. Latency Source - Destination

The minimum latency between source and destination

Min. RTT

The minimum RTT

MOS

The MOS

Packets Lost

The number of lost packets

Packets Lost %

The number of lost packets (%)

Packets Out of Sequence

The number of out-of-sequence packets

More

i_square_blueKNOWLEDGE BASE

What security features does PRTG include?