ILOM Out-of-Memory due to Nessus security scan

Asset ID:	1-72-2391782.1
Update Date:	2018-04-26
Keywords:

Solution Type Problem Resolution Sure

Solution 2391782.1 : ILOM Out-of-Memory due to Nessus security scan

Applies to:

SPARC T4-1B - Version All Versions and later
SPARC T4-1 - Version All Versions and later
SPARC T3-1 - Version All Versions and later
SPARC T3-2 - Version All Versions and later
SPARC T3-4 - Version All Versions and later
Information in this document applies to any platform.

Symptoms

ILOM is hung & must be restarted via the Serial Management port or the chassis/blade must be powercycled/reseated.

Servers contain the following message in the event log:
984 Sun Jun 23 10:59:32 2017 System Log critical System restarted due to Out-Of-Memory condition.

CMMs will see the following problems with blades:
2017-12-27/13:46:16 257f8e85-21cc-623c-f6a4-c5825e8dc09c SPX86-8000-1D Critical Chassis Device Failure
2018-02-05/07:33:29 ereport.fs.dir.coredump-full@/CH/CMM/SP

Cause

Too many concurrent security scanner threads

Solution

Please note that ILOM firmware prior version 3.2.4 resolved many memory leak problems, so a firmware update to a recent version will correct that problem.

The ILOM allows 10 concurrent users to be logged in via ssh or web sessions. The Nessus/security scanner can be configured to with multiple concurrent ssh & web sessions.

The security scanner must limit the number of concurrent ssh / web sessions to 2 for each ILOM. Too many have adversely affected some customer's systems as shown above.

References

<BUG:26330891> - ILOM OOM ON 3.2.9.1.B & PRIOR

Attachments

This solution has no attachment