The "Memory" Usage and the "Physical Memory" Utilization are calculated differently by Orion NPM.
The Memory is the sum of the memory used by the processes listed in the HOST-RESOURCES-MIB:hrSWRunPerfTable (184.108.40.206.220.127.116.11.1).
The OID used is the hrSWRunPerfMem (18.104.22.168.22.214.171.124.1.1.2).
The Physical Memory is calculated based on the values populated in the HOST-RESOURCES-MIB:hrStorageTable (126.96.36.199.188.8.131.52.2.3).
The OIDs used are hrStorageSize (184.108.40.206.220.127.116.11.3.1.5), hrStorageUsed (18.104.22.168.22.214.171.124.3.1.6) and hrStorageAllocationUnits (126.96.36.199.188.8.131.52.3.1.4) .
Depending how the SNMP agent on the host is reporting values, it can lead to some discrepancies between the two results.
I would advise you to use the most accurate between both and unmanage the other element.
Results will vary depending of the plaftorms.
I hope this helps you.
Great, that help :-)
Thx & BR
We also have the same issue with conflicting results from the radial dial (CPU & Memory Utilization) v Physical & Virtual (Volume Utilization) . It seems that the simplest way to remove the incorrect radial dial erroneos value is to unmanage this as suggested above, but this is tied to the CPU tracking. So if we lose the incorect memory, we also lose the correct CPU logging. Is there a way to only deselect the memory part of the CPU & Memory Utilization check box?
Or will this be repaired, made consistent, or made an option soon?