-
Products
-
SonicPlatform
SonicPlatform is the cybersecurity platform purpose-built for MSPs, making managing complex security environments among multiple tenants easy and streamlined.
Discover More
-
-
Solutions
-
Federal
Protect Federal Agencies and Networks with scalable, purpose-built cybersecurity solutions
Learn MoreFederalProtect Federal Agencies and Networks with scalable, purpose-built cybersecurity solutions
Learn More - Industries
- Use Cases
-
-
Partners
-
Partner Portal
Access to deal registration, MDF, sales and marketing tools, training and more
Learn MorePartner PortalAccess to deal registration, MDF, sales and marketing tools, training and more
Learn More - SonicWall Partners
- Partner Resources
-
-
Support
-
Support Portal
Find answers to your questions by searching across our knowledge base, community, technical documentation and video tutorials
Learn MoreSupport PortalFind answers to your questions by searching across our knowledge base, community, technical documentation and video tutorials
Learn More - Support
- Resources
- Capture Labs
-
- Company
- Contact Us
Memory allocation failures for systems with SonicOS 6.2.5.2+ or 6.2.6.0+
03/26/2020 
4 People found this article helpful
484,314 Views
Description
Some SonicWall customers are experiencing memory allocation failures in some GEN6 firmware with SonicOS 6.2.5.2+ or 6.2.6.0+ 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.
Resolution
Customers who are running into memory allocation failure issues for firewalls running SonicOS 6.2.5.2+ or 6.2.6.0+ 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 6.2.5.2/6.2.5.3 use 6.2.5.3-35n--HF180349-3n: \dfs3SWBuildsGEN66.2.5.3-35n--HF180349-3n
- For customers running SonicOS 6.2.6.0/6.2.6.1 use 6.2.6.1-25n--HF180264-3n: \dfs3SWBuildsGEN66.2.6.1-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 6.2.7.0-17n."
Related Articles
- How to Block Google QUIC Protocol on SonicOSX 7.0?
- How to block certain Keywords on SonicOSX 7.0?
- How internal Interfaces can obtain Global IPv6 Addresses using DHCPv6 Prefix Delegation
Categories
- Firewalls > TZ Series
- Firewalls > SonicWall SuperMassive E10000 Series
- Firewalls > SonicWall SuperMassive 9000 Series
- Firewalls > SonicWall NSA Series
YES
NO