CiscoAnyConnect Active Sessions

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.

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. 

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.

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.

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.

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?

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.

I have been seeing session numbers much higher than I would expect.  When I looked closer the numbers are not matching the output from manually checking using the CLI.  This is across a few dozen devices with different setups.  I think the OID may be different I found the following ones that I am testing. I will post back if I get better results:

As an FYI - 

I have added the following OID to the datasource I have downloaded so that we can see the Maximum Session count (Raw Data) - this may be of use to others as well.

alSslStatsMaxSessions  - 1.3.6.1.4.1.3076.2.1.2.26.1.3.0 
Description - "The maximum number current of active sessions at any one time."

On 3/17/2020 at 4:20 PM, Stuart Weenig said:

Check now. It should be good to go.

Thanks for getting this pushed through, with all that's going on at the moment it saved a little time in putting something like this together.

& Thanks to @Sawer.lef for publishing in the first place