Negative values in Orion.ASA.RemoteAccessDetail

When the values get large enough, they become negative. The schema says these are int64 values too, so it should be able to handle the values. If you want to know which ones - any of the InPkts, OutPkts, InBps, OutBPS, inBytes, outBytes etc. I ran a top 1000 query at the entity as I was concerned my swql did something weird. No change. What am I missing? Or have I stumbled onto another hidden feature request that needs to be made public.

Tested on SolarWinds Orion Platform 2023.2. Although I suspect other versions are affected.

Find more posts tagged with

remote access vpn

asa

vpn

npm

remote access sessions

Accepted answers

All comments

marcrobinson

Digging deeper, it looks like this is a calculated and stored value in int64 format. If I found out more, I will post back. NOTE - the issue only appears when values get big, BIG. I just have not found the spot where things get negative...

adam.beedell

Negative sounds like a overflow error, and int64 is massive, I'd guess there's a polling script of some sort that handles a standard less than int64 such that the database can handle it but something else doesnt. The limits to look for would be like one of these probably:

`int`	4	`signed`	2,147,483,647



`__int16`	2	`short`, `short int`, `signed short int`	32,767


`unsigned __int32`	4	`unsigned`, `unsigned int`	4,294,967,295

Any of those look like they line up?

Or the numbers polled are stupid-clearly-an-error massive, and we should get the database type switched to unsigned int64 to double the positive range. No need for a negative range I can think of.

marcrobinson

After upgrading to 2023.3 - still seems to be happening. I agree with your analysis above. I just opened a ticket to see if I am missing something else, bad polling jobs, or the devices have a sense of humor when returning metrics. I hope it is not the last as that would mean they are already plotting to take over the world. Joking aside, I will post back an answer.

marcrobinson

It looks like a bug as the issue was escalated to the Dev. They have been working on it. No news yet. If I had to guess - 2023.4 might see the fix.