RSA Authentication Manager shows high memory utilization when running top, free or vmstat and some SNMP traps
15 days ago
Originally Published: 2010-03-23
Article Number
000045836
Applies To

RSA Product Set: SecurID 
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x
 

Issue
  • RSA Authentication Manager ver. 8.x show free memory that is less than available memory.
  • Some SNMP traps for high memory utilization can be triggered even when the system is idle. 

Do Linux free, vmstat and top commands accurately show the amount of free RAM?

Key Insight: The "free" memory in free and top is not the only usable memory. Linux uses unused RAM for buffers and cache to speed up disk operations. This memory is available for applications when needed, so "available" (from free) is the true measure of free RAM.

Cause

Linux uses a memory management known as "lazy man" memory mapping to speed up disk access. But this memory allocated for disk access is readily available to applications when needed. Therefore Linux commands such as free, top and vmstat show both used and available memory.

"Available" memory is the true measure of free RAM in the Linux on the RSA Authentication Manager Appliances.


In such a memory management/kernel approach, (scroll to the second to the last paragraph of the page on this link):

To make the most efficient use of real memory, Linux automatically uses all free RAM for buffer cache, but also automatically makes the cache smaller when programs need more memory.

Resolution

Linux commands such as free, top and vmstat show both used and available memory.

top_vs_free_lazy_man_memory.png 
"Available" memory is the true measure of free RAM in the Linux on the RSA Authentication Manager Appliances.

Use available memory as the most accurate indicator of free RAM for starting new applications on your AM appliance.

 

Workaround

Use available memory as the most accurate indicator of free RAM for starting new applications on your AM appliance.

Notes

You can also use an SNMP OID for the trap vs free output.  For more information on SNMP traps on Linux, reference this article on Linux SNMP OIDs for CPU,Memory and Disk Statistics.

You should consider the use of the UCD OID .1.3.6.1.4.1.2021 for CPU and memory usage versus using HOST MIBs, noting all reported available thresholds report in kilobytes.

Authentication Manager 8.1 SNMP OIDs

  • Total physical memory for the operating system memory in KB: .1.3.6.1.4.1.674.10892.1.400.20.1.5
  • Available physical memory for the operating system memory in KB.: .1.3.6.1.4.1.674.10892.1.400.20.1.6

Complete list of UCD MIB OIDS for older RSA SecurID Appliance 3.0

DescriptionOID
Total Swap Size1.3.6.1.4.1.2021.4.3.0
Available Swap Space1.3.6.1.4.1.2021.4.4.0
Total RAM in Machine1.3.6.1.4.1.2021.4.5.0
Available Real Memory1.3.6.1.4.1.2021.4.6.0
Total RAM Free1.3.6.1.4.1.2021.4.11.0
Total RAM Shared1.3.6.1.4.1.2021.4.13.0
Total RAM Buffered1.3.6.1.4.1.2021.4.14.0
Total Cached Memory1.3.6.1.4.1.2021.4.15.0

For additional information on hardware SNMP traps for Authentication Manager 8.1 or the RSA SecurID Appliance 3.0, see the RSA Authentication Manager 8.1 SNMP Reference Guide, Revision 1 or the RSA SecurID Appliance 3.0 SNMP Reference Guide.