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).
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- 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
- In certain cases, the object identifiers (OID) that the sensor uses are not available on the target device. The sensor shows the following error message: No such object (SNMP error # 222). If you encounter this issue, open the SNMP Compatibility Options setting of the parent device or group and set the Request Mode to Use single get.
- 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.
- This sensor has a low performance impact.
- This sensor only supports the IPv4 protocol.
- This sensor uses lookups to determine the status values of one or more channels. This means that possible states are defined in a lookup file. You can change the behavior of a channel by editing the lookup file that the channel uses. For details, see section Define Lookups.
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.
Setting |
Description |
---|---|
IP SLAs |
Select the IP SLAs that you want to monitor. PRTG creates one sensor for each SLA that you select. The list options depend on the configuration of the target device that you query. If a type is missing, check the configuration of the target device. The sensor can support the following operations with the specified type IDs:
|
Click the Settings tab of a sensor to change its settings.
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. |
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:
|
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.
IP SLA Specific
Setting |
Description |
---|---|
ID |
Shows the ID of the SLA that this sensor monitors.
|
Type |
Shows the type of the SLA that this sensor monitors.
|
Name (Tag) |
Shows the name of the SLA that this sensor monitors.
|
Owner |
Shows the owner of the SLA that this sensor monitors.
|
Frequency |
Shows the frequency of the SLA 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:
|
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 the following 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.
Click to interrupt the inheritance.
Setting |
Description |
---|---|
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:
|
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:
|
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.
Setting |
Description |
---|---|
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:
|
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:
|
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:
|
Dependency |
This setting is only visible if you enable Select a sensor above. Click |
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.
|
Click to interrupt the inheritance.
Setting |
Description |
---|---|
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:
|
Which channels the sensor actually shows might depend on the monitored device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Avg. Jitter |
The average jitter in milliseconds (msec) |
Avg. Jitter Destination - Source |
The average jitter between destination and source in msec |
Avg. Jitter Source - Destination |
The average jitter between source and destination in msec |
Avg. Latency Destination - Source |
The average latency between destination and source in msec |
Avg. Latency Source - Destination |
The average latency between source and destination in msec |
Average Round Trip Time (RTT) |
The average round-trip time (RTT) in msec
|
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. |
ICPIF |
The Impairment Calculated Planning Impairment Factor (ICPIF) |
Late Packets |
The number of late packets |
Max. Latency Destination - Source |
The maximum latency between destination and source in msec |
Max. Latency Source - Destination |
The maximum latency between source and destination in msec |
Max. RTT |
The maximum RTT in msec |
Min. Latency Destination - Source |
The minimum latency between destination and source in msec |
Min. Latency Source - Destination |
The minimum latency between source and destination in msec |
Min. RTT |
The minimum RTT in msec |
MOS |
The mean opinion score (MOS) |
Packets Lost |
The number of lost packets |
Packets Lost % |
The number of lost packets in percent |
Packets Lost |
The number of out-of-sequence packets |
Knowledge Base
What security features does PRTG include?
For more information about sensor settings, see the following sections: