![background image](http://html1.mh-extra.com/html/d-link/netdefend-dfl-260e/netdefend-dfl-260e_log-reference-manual_3185262525.webp)
2.46.7. processing_memory_limit_reached (ID: 04800009)
Default Severity
Log Message
Maximum processing memory limit reached
Explanation
The reassembly subsystem has reached the maximum limit set on its
processing memory. This will decrease the performance of
connections that are processed by the reassembly subsystem.
Gateway Action
drop
Recommended Action
Consider increasing the setting Reassembly_MaxProcessingMem.
Revision
1
2.46.8. maximum_connections_limit_reached (ID: 04800010)
Default Severity
Log Message
Maximum connections limit reached
Explanation
The reassembly subsystem has reached the maximum number of
concurrent connections.
Gateway Action
none
Recommended Action
Consider increasing the setting Reassembly_MaxConnections.
Revision
1
Context Parameters
2.46.9. state_memory_allocation_failed (ID: 04800011)
Default Severity
Log Message
Failed to allocate the memory needed to activate reassembly on a
connection
Explanation
The reassembly subsystem has failed to allocate the memory
needed to activate reassembly on a connection.
Gateway Action
none
Recommended Action
Review configuration to reduce memory consumption.
Revision
1
Context Parameters
Chapter 2: Log Message Reference
525
Summary of Contents for NetDefend DFL-260E
Page 32: ...List of Tables 1 Abbreviations 35 32...
Page 33: ...List of Examples 1 Log Message Parameters 34 2 Conditional Log Message Parameters 34 33...
Page 42: ...routemetric Route metric cost Chapter 1 Introduction 42...
Page 44: ...Chapter 1 Introduction 44...
Page 216: ...Rule Information Connection Chapter 2 Log Message Reference 216...
Page 243: ...client_ip Context Parameters Rule Name Packet Buffer Chapter 2 Log Message Reference 243...
Page 556: ...logger Chapter 2 Log Message Reference 556...
Page 613: ...Parameters location Chapter 2 Log Message Reference 613...