5 Replies Latest reply on Jun 23, 2017 8:25 AM by mprobus

Wrong values in database for VM memory

bleearg13 Jun 22, 2017 9:50 AM

I considered posting this in the Virtualization Manager forum, but I think this is an NPM issue. I occasionally have VMs that alert due to high memory, but the issue is really that Orion is putting the wrong values in the database. Let me explain with a picture:

As you can see in the left-hand column, the highlighted part shows 'Memory usage of this guest', which is supposed to be a percentage. It is instead showing the actual value of the memory being used, rather than a percentage, which you can see in the right-hand column. The corresponding VM in VMAN shows '50%' usage everywhere, too.

Is this a reported bug or has anyone else seen this before?

Re: Wrong values in database for VM memory

mesverrum Jun 22, 2017 7:36 PM (in response to bleearg13)

Thats a new bug to me, I have used VMAN and NPM in dozens of environments and not seen that yet. Did you open a ticket?
Like (0)

Actions
- Re: Wrong values in database for VM memory
  
  bleearg13 Jun 23, 2017 6:25 AM (in response to mesverrum)
  
  I have not. I wanted to see if there was a quick fix prior to doing so, because my last VMAN/VIM ticket was opened in February and is still open with no end in sight.
  
  Like (0)
  
  Actions
Re: Wrong values in database for VM memory

mprobus Jun 23, 2017 7:02 AM (in response to bleearg13)

What version of NPM and IVIM are you using? I had a similar issue when doing the POC on SAM, but it's resolved now. I tried looking through my emails and found where I sent the issue to Solarwinds, but we apparently met to resolve it so I don't have documentation on what was done.
Like (0)

Actions
- Re: Wrong values in database for VM memory
  
  bleearg13 Jun 23, 2017 8:21 AM (in response to mprobus)
  
  NPM 12.1 and VIM 7.1.0.
  
  Like (0)
  
  Actions
Re: Wrong values in database for VM memory

mprobus Jun 23, 2017 8:25 AM (in response to bleearg13)

In that case, then it sounds like a support ticket is your best route. Since I was in POC when I had the issue, I don't have a case I can go back and reference. I did find in my emails where I had to update a couple of dlls around the same time, but I am not sure if they were for this exact issue. And that was multiple versions of SAM and VMAN ago, so my guess is that they would be incorporated into the build now.
Like (0)

Actions

Go to original post