RSA Product Set: SecurID
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x
- 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.
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.
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.
Use available memory as the most accurate indicator of free RAM for starting new applications on your AM appliance.
Use available memory as the most accurate indicator of free RAM for starting new applications on your AM appliance.
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
| Description | OID |
| 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 |
| Available Real Memory | 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 |
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.
Related Articles
AFX Server stuck in 'Not running' State, with error 'timed out waiting for AFX applications to start' 3.61KNumber of Views AFX Connectors remain in a Deployed state and ActiveMQ is not running in RSA Identity Governance & Lifecycle 459Number of Views Best practices for running vulnerability scans against RSA Authentication Manager 8.x 1.09KNumber of Views RSA Authentication Manager 8.x - Weak Ciphers Vulnerabilities found with Qualys Scan - Updated 1.52KNumber of Views Running ./rsaserv command displays errors on the log4j file for RSA Authentication Manager 8.x 1.35KNumber of Views
Trending Articles
RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide How to Download OTP Token Seed Files from myRSA Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU