Solarwind OID details for CentOS7

Selvin9578 · 03-31-2017, 05:59 AM

Dear team,

I have one doubt for the Solarwind OID. We have the below OID in solarwind..

Total Swap Size: .1.3.6.1.4.1.2021.4.3.0
Available Swap Space: .1.3.6.1.4.1.2021.4.4.0
Total RAM in machine: .1.3.6.1.4.1.2021.4.5.0
Total RAM used: .1.3.6.1.4.1.2021.4.6.0
Total RAM Free: .1.3.6.1.4.1.2021.4.11.0
Total RAM Shared: .1.3.6.1.4.1.2021.4.13.0
Total RAM Buffered: .1.3.6.1.4.1.2021.4.14.0
Total Cached Memory: .1.3.6.1.4.1.2021.4.15.0

But this one not showing available RAM space. Can you share the exact OID or MIB file to me asap.

Regards,
Selvin Durai

rtmistler · 03-31-2017, 07:21 AM

This would seem to be more of a specific question to the creators of the product advertising that MIB.

However, you seem to be asking about available RAM space.

Where do you not see this information? Since the MIB shows total RAM in machine, total used, and total free.

jefro · 03-31-2017, 03:57 PM

Think this link explains where they come from and how to update them. https://thwack.solarwinds.com/commun...to-manage-them

About zero chance anyone can provide it. You have to get it from the system.

r3sistance · 03-31-2017, 06:05 PM

available RAM statistics are usually just estimates... If you're looking for the unallocated RAM, then take the total RAM and minus the used, shared, cached and buffers from it. However the available RAM will be somewhere between the unallocated RAM and the unallocated RAM minus the buffers/cache memory... since most buffer and cache memory is likely to be low priority meaning the memory is available for other programs to use at their leisure. Maybe somebody else can give a better description of it.

Anyways you're using SNMP here, so you could get any old SNMP tool and use it to scan the server yourself. May need to do some work on the snmpd.conf tho.

Personally when it comes to memory statistics, I prefer to use sysstat over facilities such as solarwinds. The commit% given by sysstat is usually more useful for figuring out just how heavily loaded a server really is on memory. I usually advise memory upgrades myself, when commit% is going over 40% on a fairly regular basis but it does depend on what you are doing (I.E. KVM host 80% commit maybe find).