Memory allocation failures for systems with SonicOS 184.108.40.206+ or 220.127.116.11+
03/26/2020 4 10614
Some SonicWall customers are experiencing memory allocation failures in some GEN6 firmware with SonicOS 18.104.22.168+ or 22.214.171.124+ and the issue is becoming more wide spread.
This article is for L1 support engineers information and L2 support engineers will be responsible for recommending the appropriate hot fix for the issue and gathering the log files for further investigation.
For more details about the issue and the the changes in the new builds, please refer to DTS 180264 and 180349.
Customers who are running into memory allocation failure issues for firewalls running SonicOS 126.96.36.199+ or 188.8.131.52+ are recommended following steps.
Step1: Download and upgrade the relevant of below hotfix builds which include improved diagnostics in case any other memory versus some corruption causing memory allocation failures:
- For customers running SonicOS 184.108.40.206/220.127.116.11 use 18.104.22.168-35n--HF180349-3n: \dfs3SWBuildsGEN22.214.171.124-35n--HF180349-3n
- For customers running SonicOS 126.96.36.199/188.8.131.52 use 184.108.40.206-25n--HF180264-3n: \dfs3SWBuildsGEN220.127.116.11-25n--HF180264-3n
Step2: As customer environment permits, collecting Trace Logs and/or Console logs every few days for two to three weeks after loading will help. ( Hook up of the console port for this not required however providing console logs may provide additional data. Logs will provide Escalation and R&D for critical diagnostic information, if these systems experience a repeat of the problem.)
Note: Any questions or follow ups require, please contact your manager or Escalation team at SEEGUTM@SonicWall.com.
Update: As per Comment #29 in DTS 180264 and Comment #51 in DTS 180349:
"The fixes are all included in 6.2.7 so changing to QA Ready - fixed in 18.104.22.168-17n."