CiscoAnyConnect Active Sessions

I was able to get accurate results changing the OID polled to:

1.3.6.1.4.1.9.9.392.1.3.35 under the properties, and 1.3.6.1.4.1.9.9.392.1.3.35.0 under the data source.

Awesome and thank you, it's working great for my ASAs in the system.  Anyone have one to monitor the same thing on the Cisco FPR devices?

You can use this same OID to monitor on FPR devices.  Just adjust your applies too to include fire power devices (if you are using the the OID's I posted about).  I don't believe the original OIDs worked for firepower for me but the one I updated with did.

Thank you Matt.  I'm confused about where to actually change the OID's that you posted. Are you changing on the datasource and then under parameters?  Or somewhere else?  Basically i changed what it was in that location to 1.3.6.1.4.1.9.9.392.1.3.35.0 and applied to a FTD but it didn't seem to work.  I'm not sure that i did incorrectly.

I can't export mine and share it that way because the Exchange is being re-worked.  Here is a copy of my XML (https://pastebin.com/GErayzCE) -- you can save that locally as a XML file and then add it to your tenant by doing DataSources -> Add -> From a file, and selecting your created file.

Note -- I added a category to the "applies to" called CiscoFirePower.  You have to add that to any firepower device that you want this to apply to, and then run another active discovery.

I've uploaded but it doesn't seem to be working for any of the 2100 or 4100 series devices in my system.  I'm still playing with it a little.  I did have to change your appliesto to hasCategory("CiscoFirepowerSNMP").  None of my devices have CiscoFirepower as a category. 

Let me know how you make out.  I can confirm that its working for us at least with two different 2110 devices.  The documentation for the 2110s actually says they still use ASA SNMP OIDs and that you can still use the same entries.  I just added my devices to my Applies To and it worked great.

What you'll need to do is make sure that the datasource is getting "applied" to the additional devices. It sounds like the OIDs and stuff are probably the same between the two, so you would only need to change the "AppliesTo". You can do that manually by adding " || displayName == '[the display name of an additional device]'" to the current applies to. If that gets you data on the 2110, you'll need to further adjust the AppliesTo so that the datasource is trying to collect data for the additional devices. You can do this with a system.category, or a sysOID mapping, or a property source. 

Thank you Matt and Stuart.  Unfortunately even after setting the displayName in the appliesto isn't working.  I'm having one of the guys take a look as i just noticed that NetFlow is working but we aren't getting any SNMP info...

You can check that your appliesto is working properly (click test applies to and click the link to view the results and ensure your new device is in there). If that's successful, that part is done.

Then you can test the active discovery to see if it's discovering anything. If that part's not working, there's a problem with SNMP or the OIDs specified in discovery aren't there on the version of the device you have (doesn't sounds like the latter should be the case).

If all that works, you can test the polling by going to the device, browsing to the datasource, then the raw data tab. Click poll now to see if you're getting data back.  If that doesn't work, then there's a problem with SNMP (permissions maybe, v3?) or the OIDs specified in the "Datapoints" section of the DS aren't correct.