Hi,

I have the issue when trying to add a Cisco IP SLA sensor that in step 2 of 2 under IP SLA Specific, the message No IP SLAs available appears.

Why I click continue, I get this error message:

Oops... Nothing was selected, no sensors could be created.

The PRTG version I'm using is 12.4.7.3506, the trial license I'm using is expired. Maybe that is part of the issue?


Article Comments

you can request another trial key and extend your trial that way.

But that is probably not the cause of the issue.

Is SNMP working in general on the device, and are IPSLAs configured on the Cisco device?


Jan, 2013 - Permalink

It is working now. The trick is to first enable SNMP and IP SLA on the Cisco device and then add the IP SLA sensor in PRTG.

thanks.


Jan, 2013 - Permalink

Currently, there's a known-limitation on the new Cisco ASA 5500-X Series Firewalls which prevents them from reporting SLA metrics via SNMP, this means that trying to monitor these devices always results in:

No IP SLAs detected on this device. (code: PE192)

Please refer to Cisco's Bug Search for a current status on the subject, the ID is CSCui53368.

Status as of 29/06/2016:


Description

Symptom: The ASA does not currently support polling any OIDs to track IP SLA information via SNMP.

Conditions: This is an enhancement request to track the possibility of adding a MIB for this feature in a future release.

Workaround: N/A

Details

Last Modified: Mar 10,2016

Status: Open

Severity: 6 Enhancement

Known Affected Releases: 8.4(5)


Best Regards,
Luciano Lingnau [Paessler Support]


Jun, 2016 - Permalink

Hello,

Just wondering if there is a work around for a Cisco 5520 device? I looked up the cisco bug and its been closed.


Aug, 2017 - Permalink

Hello gkim,
thank you for your reply.

I'm afraid that there are no workarounds if the relevant MIB isn't implemented/supported by the SNMP Agent. I encourage you to ask that question to Cisco's support, as to why they have decided to not implement this for this device. According to the CSCui53368: No release planned to fix this bug

Best Regards,
Luciano Lingnau [Paessler Support]


Aug, 2017 - Permalink