Was reviewing our SAM license the other day and noticed that it showed 184 volumes under the license count. When I check SAM it only shows 102 licenses. Just curious why they show different values. Pretty sure SAM is correct.
Both licensing number and "SAM" number are SAM numbers ... anyway, when you say you have checked SAM - what/where did you actually checked?
From the Home tab I clicked on environment where it shows things like applications, servers, volumes.
The AppStack Environment view shows only volumes associated with servers and hosts. It does not show volumes associated with network devices such as routers and switches. This is the most likely reason for the discrepancy.
When I look at non-server devices they show no volumes but when I look at things like our LEM and Virtualization Manager appliances they do show the volumes that reside on the ESXi hosts they are on. Still doesn't add up to the amount the license shows but maybe it double counts the volumes. I was thinking a volume as shown in SAM was a disk volume that existed on a monitored server.
Edit:
N/M count on the report still shows 102 volumes (exported to Excel to count them)
bang on! well done, thanks for the update
spoke too soon, see edit in my previous post. Now maybe the All Volumes report isn't what it says it is either but I would think that would show what SAM knows about.
Final reply with the answer. So the first report I ran was called All Disk Volumes Inventory Report, that shows the number that SAM shows as the total number of volumes. There's another report called All Disk Volumes, that shows disks, virtual memory and physical memory which apparently are all considered disk volumes. That total adds up to 184. Wouldn't have ever thought that the volume count in the license was based on those three items but that seems to be the case.
Indeed so - both Virtual Memory and Physical memory will count towards your licenses for Volumes if you will select them in "List Resources". I would suggest you to not add any of those as SolarWinds is monitoring memory as part of Node license already. You can see this by adding "Memory Utilisation" resource(s) on your node page. Adding this additional Virtual/Physical memory as a Volume will apparently (as you have discovered) eat your license points. I am not sure if there are any benefits of having them monitored as Volumes in addition to what is being monitored as memory.
