These log messages refer to the REASSEMBLY (Events concerning data reassembly) category.
2.55.1. ack_of_not_transmitted_data (ID: 04800002)
- Default Severity
- INFORMATIONAL
- Log Message
- TCP segment acknowledges data not yet transmitted
- Explanation
- A TCP segment that acknowledges data not yet transmitted was received. The segment will be dropped.
- Firewall Action
- drop
- Recommended Action
- None
- Revision
- 1
- Context Parameters
- Connection
2.55.2. invalid_tcp_checksum (ID: 04800003)
- Default Severity
- NOTICE
- Log Message
- TCP segment with invalid checksum
- Explanation
- A TCP segment with an invalid checksum was received. The segment will be dropped.
- Firewall Action
- drop
- Recommended Action
- None
- Revision
- 1
- Context Parameters
- Connection
2.55.3. mismatching_data_in_overlapping_tcp_segment (ID: 04800004)
- Default Severity
- ERROR
- Log Message
- Overlapping TCP segment containing different data
- Explanation
- A TCP segment that partly overlaps segments that has been received earlier was received. The data in the overlapping part
is however different from the data in the segments received earlier. The segment's data will be replaced so that it is consistent
with the earlier received segments.
- Firewall Action
- correct the data
- Recommended Action
- Research the source of this errornous traffic.
- Revision
- 1
- Context Parameters
- Connection
2.55.4. memory_allocation_failure (ID: 04800005)
- Default Severity
- ERROR
- Log Message
- Can't allocate memory to keep track of a packet
- Explanation
- The firewall is unable to allocate memory to keep track of packet that was received. The packet will be dropped.
- Firewall Action
- drop
- Recommended Action
- Review configuration to reduce memory consumption.
- Revision
- 2
2.55.5. drop_due_to_buffer_starvation (ID: 04800007)
- Default Severity
- ERROR
- Log Message
- Can't allocate resources to process a packet
- Explanation
- The firewall ran out of resources when trying to allocate resources to send a packet. The packet that triggered the need to
send a packet will be dropped.
- Firewall Action
- drop
- Recommended Action
- Check buffer consumption.
- Revision
- 2
2.55.6. failed_to_send_ack (ID: 04800008)
- Default Severity
- ERROR
- Log Message
- Failed to send TCP ACK in response to a segment
- Explanation
- The firewall responds to some segments by sending an acknowledgement segment to the sender. An example is when it receives
a segment that is outside of the receiver's receive window. This log message indicates that the firewall failed to allocate
resources to send such an acknoledgement segment.
- Firewall Action
- None
- Recommended Action
- Check buffer consumption.
- Revision
- 2
2.55.7. processing_memory_limit_reached (ID: 04800009)
- Default Severity
- NOTICE
- 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.
- Firewall Action
- drop
- Recommended Action
- Consider increasing the setting Reassembly_MaxProcessingMem.
- Revision
- 1
2.55.8. maximum_connections_limit_reached (ID: 04800010)
- Default Severity
- NOTICE
- Log Message
- Maximum connections limit reached
- Explanation
- The reassembly subsystem has reached the maximum number of concurrent connections.
- Firewall Action
- None
- Recommended Action
- Consider increasing the setting Reassembly_MaxConnections.
- Revision
- 1
- Context Parameters
- Connection
2.55.9. state_memory_allocation_failed (ID: 04800011)
- Default Severity
- ERROR
- 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.
- Firewall Action
- None
- Recommended Action
- Review configuration to reduce memory consumption.
- Revision
- 1
- Context Parameters
- Connection
cOS Core 14.00.18 Log Reference Guide
