Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Remote access VPN reporting issue

We recently migrated our NPM instance from a physical to virtual environment.

After migrating to the virtual environment, the Remote Access VPN connection details on our ASA's do not show the correct data in the database.

For example, it seems like the data is 'stuck' after the migration.

If i examine in NPM the Remote Access VPN connection tab on my ASA, it shows 4 connections active on the day of migration, and it still thinks that these connections are active when they are not.

When the 'users' connect again today, it appears to think that they have always been connected and just extends their duration, saying that they have been connected for X number of days.

If there anyway to force a refresh of this data, so that it only shows the current connections?

See below for what i mean.

Find more posts tagged with

Accepted answers

dunky2k

Issued was resolved by deleting the existing ASA Nodes and then re-adding them again to force refresh of data.

All comments

alansmith

I built a customer Universal Device Poller to pull this information and created custom pages for each vpn. Then built a custom report with the UDP information. You will want to pull the specific OID numbers to build the custom UDP information on the server itself.

dunky2k

@alansmith I have a custom UDP configured already pulling this information to a custom page.

The issue that i have is that the report no longer shows any users connected since we did the migration, but from the firewall module itself i can see the correct number of users connected.

It appears as if the session details are 'stuck' somewhere in the database, that perhaps either need deleted or a refresh forced to remove them.

The Node page of the ASA as listed above shows these users as being active for over 4 days, when the physical cisco asdm module does not show them as connected users.

I need some sort of mechanism that will 'refresh' the true data back to the Solarwinds DB.

alansmith

Check on the device polling rate.

dunky2k

Polling rate completion is fine - its less that 70% for both pollers.

dunky2k

Issued was resolved by deleting the existing ASA Nodes and then re-adding them again to force refresh of data.